Basic CTE with a Join

USE AdventureWorks2008
GO
;WITH VendorCTE AS (
 SELECT Vendor.AccountNumber, Vendor.BusinessEntityID, Vendor.Name
 FROM Purchasing.Vendor WHERE CreditRating = 2), 
 OrderCTE AS 
 (SELECT  VendorID, SUM(TotalDue) AS SumTotalDue 
 FROM Purchasing.PurchaseOrderHeader POH
 JOIN Purchasing.PurchaseOrderDetail POD
 ON POH.PurchaseOrderID  = POD.PurchaseOrderID
 WHERE UnitPrice > 25.00
 GROUP BY VendorID)

Convert Text Data to DATETIME using STUFF method

--create a table emulating a fixed-width text import
DECLARE @Imports TABLE (
 DATEFIELD char(19) NOT NULL,
 DATAFIELD char(10) NOT NULL )
INSERT INTO @Imports VALUES
('2010:09:09 16:00:46','$    10.88'),
('2010:09:16 13:56:41','$    21.68'),
('2010:09:16 14:05:50','$     5.57'),
('2010:09:19 16:43:31','$    15.33'),
('2010:09:19 18:42:21','$   259.23'),
('2010:09:25 13:50:29','$    73.79'),
('2010:09:25 13:50:37','$    46.92')
 
SELECT DATEFIELD,
 CONVERT(DATETIME, STUFF(STUFF(DATEFIELD, 8,1,''),5,1,'')) AS [DATEFIELD Converted],
FROM @Imports

Search SQL Server Agent Job Steps for Specific Keyword Text or Stored Procedure

USE [msdb]
GO
SELECT j.job_id,
 s.srvname,
 j.name,
 js.step_id,
 js.command,
 j.enabled 
FROM dbo.sysjobs j
JOIN dbo.sysjobsteps js
 ON js.job_id = j.job_id 
JOIN master.dbo.sysservers s
 ON s.srvid = j.originating_server_id
WHERE js.command LIKE N'%KEYWORD_SEARCH%'
GO

What is the best way to auto-generate INSERT statements for a SQL Server table

DECLARE @Fields VARCHAR(max); SET @Fields = '[QueueName], [iSort]' -- your fields, keep []

DECLARE @Table  VARCHAR(max); SET @Table  = 'Queues'               -- your table

DECLARE @SQL    VARCHAR(max)

SET @SQL = 'DECLARE @S VARCHAR(MAX)

SELECT @S = ISNULL(@S + '' UNION '', ''INSERT INTO ' + @Table + '(' + @Fields + ')'') + CHAR(13) + CHAR(10) + 

 ''SELECT '' + ' + REPLACE(REPLACE(REPLACE(@Fields, ',', ' + '', '' + '), '[', ''''''''' + CAST('),']',' AS VARCHAR(max)) + ''''''''') +' FROM ' + @Table + '

PRINT @S'

EXEC (@SQL)

RESULTS WILL BE LYK:-

INSERT INTO Queues([QueueName], [iSort])

SELECT 'WD: Auto Capture', '10' UNION 

SELECT 'Car/Lar', '11' UNION 

SELECT 'Scan Line', '21' UNION 

SELECT 'OCR', '22' UNION 

SELECT 'Dynamic Template', '23' UNION 

SELECT 'Fix MICR', '41' UNION 

SELECT 'Fix MICR (Supervisor)', '42' UNION 

SELECT 'Foreign MICR', '43' UNION 

...

Specify a Custom Application Name to Distinguish Excel Applications

If you create Excel worksheets or PivotTables with embedded connections to SQL Server, you may want to consider changing the name of the application so you can tell which spreadsheet template someone is using. That way in Management Studio or in any logging you setup, it will your custom name.

Data Source=SQL_SERVER_OR_IP;Initial Catalog=DATABASE_NAME;Application Name=EXCEL_TEMPLATE_MASTER_REPORT;User ID=USER_NAME;Password=PASSWORD

Table Variables How and Why to use them

So what are table variables and why should I use them? There’s plenty of information out there about the table variables particularly as compared to a temporary table so let me just summarize some of the differences and point out a few use cases that are ideal for developers.
First the syntax is identical except that temporary tables are CREATED with a # while table variables are
DECLARED with a @.

CREATE TABLE #TestTable (
      ID int NOT NULL IDENTITY(1,1) PRIMARY KEY CLUSTERED,
      SomeValue varchar(30) NOT NULL
)
 
DECLARE @TestTable TABLE (

TO FIND WHICH ARE ALL TABLES HAVING IDENTITY PROPERTY

SELECT OBJECT_NAME(id) as TableName, name as ColumnName
FROM syscolumns
WHERE status = 0x80

What is Normalization?? what is the use of normalization while designing Databse

rmalization or data normalization is a process to organize the data into tabular format (database tables). A good database design includes the normalization, without normalization a database system may slow, inefficient and might not produce the expected result. Normalization reduces the data redundancy and inconsistent data dependency.

Normal Forms

We organize the data into database tables by using normal forms rules or conditions. Normal forms help us to make a good database design. Generally we organize the data up to third normal form. We rarely use the fourth and fifth normal form.

To understand normal forms consider the folowing unnormalized database table. Now we will normalize the data of below table using normal forms.

1. First Normal Form (1NF)

   A database table is said to be in 1NF if it contains no repeating fields/columns. The process of converting the UNF table into 1NF is as follows:
   1. Separate the repeating fields into new database tables along with the key from unnormalized database table.
   2. The primary key of new database tables may be a composite key
   1NF of above UNF table is as follows:
   

2. Second Normal Form (2NF)

   A database table is said to be in 2NF if it is in 1NF and contains only those fields/columns that are functionally dependent(means the value of field is determined by the value of another field(s)) on the primary key. In 2NF we remove the partial dependencies of any non-key field.
   The process of converting the database table into 2NF is as follows:
   1. Remove the partial dependencies(A type of functional dependency where a field is only functionally dependent on the part of primary key) of any non-key field.
   2. If field B depends on field A and vice versa. Also for a given value of B, we have only one possible value of A and vice versa, Then we put the field B in to new database table where B will be primary key and also marked as foreign key in parent table.
   2NF of above 1NF tables is as follows:
   

3. Third Normal Form (3NF)

   A database table is said to be in 3NF if it is in 2NF and all non keys fields should be dependent on primary key or We can also said a table to be in 3NF if it is in 2NF and no fields of the table is transitively functionally dependent on the primary key.The process of converting the table into 3NF is as follows:
   1. Remove the transitive dependecies(A type of functional dependency where a field is functionally dependent on the Field that is not the primary key.Hence its value is determined, indirectly by the primary key )
   2. Make separate table for transitive dependent Field.
   3NF of above 2NF tables is as follows:
   

4. Boyce Code Normal Form (BCNF)

   A database table is said to be in BCNF if it is in 3NF and contains each and every determinant as a candidate key.The process of converting the table into BCNF is as follows:
   1. Remove the non trival functional dependency.
   2. Make separate table for the determinants.
   BCNF of below table is as follows:
   

5. Fourth Normal Form (4NF)

   A database table is said to be in 4NF if it is in BCNF and primary key has one-to-one relationship to all non keys fields or We can also said a table to be in 4NF if it is in BCNF and contains no multi-valued dependencies.The process of converting the table into 4NF is as follows:
   1. Remove the multivalued dependency.
   2. Make separate table for multivalued Fields.
   4NF of below table is as follows:
   

6. Fifth Normal Form (5NF)

   A database table is said to be in 5NF if it is in 4NF and contains no redundant values or We can also said a table to be in 5NF if it is in 4NF and contains no join dependencies.The process of converting the table into 5NF is as follows:
   1. Remove the join dependency.
   2. Break the database table into smaller and smaller tables to remove all data redundancy.
   5NF of below table is as follows:
   
7.