Nakul,

This article is very impressive. I think I am fortunate to know you in person.

Wonderful resource. Bookmarked myself.

Great Article. I really enjoy reading this.

Many thanks for thinking 'SELECT *'. I agree that Select * now means bring me everything.

Kind Regards,

Very very nice article Love it.

Case can be used in ORDER BY as well.

http://blog.sqlauthority.com/2007/07/17/sql-server-case-statement-in-order-by-clause-order-by-using-variable/

Two different solution.

1) Create backup file timestamped in that way it will create new file everytime instead of appending all of them to one file.

2) Always truncate log using backup...

Hi,

Please visit following link, I think this should solve your problem.

http://blog.sqlauthority.com/2007/06/11/sql-server-cannot-resolve-collation-conflict-for-equal-to-operation/

This link demonstrates the usage of Rank Function for SQL Server 2005 paging technique.

http://blog.sqlauthority.com/2007/06/11/sql-server-2005-t-sql-paging-query-technique-comparison-over-and-row_number-cte-vs-derived-table/

This link demonstrates the usage of the Cross Join.

http://blog.sqlauthority.com/2007/05/15/sql-server-binary-sequence-generator-truth-table-generator/

This is good documentation of your question. Answer to your question.

http://blog.sqlauthority.com/2007/04/01/sql-server-tempdb-is-full-move-tempdb-from-one-drive-to-another-drive/

http://blog.sqlauthority.com/2006/12/20/sql-server-fix-error-14274-cannot-add-update-or-delete-a-job-or-its-steps-or-schedules-that-originated-from-an-msx-server-the-job-was-not-saved/

Some additional info

http://blog.sqlauthority.com/2007/05/11/sql-server-explanation-sql-command-go/

http://blog.sqlauthority.com/2007/04/23/sql-server-fix-error-40-could-not-open-a-connection-to-sql-server/

Hello,

http://blog.sqlauthority.com/2007/02/25/sql-server-restore-database-backup-using-sql-script-t-sql/

You are absolutely correct.

SQL Server 2005 has more strict validation which prevents bad code to pass through. It is really good. We had clean up issue, when we upgraded to...

This is sure solution.

http://blog.sqlauthority.com/2007/02/15/sql-server-fix-error-15023-user-already-exists-in-current-database/