Its been a while since I have posted, and I thought this was too amazing to NOT share

Apparently, using Check Constraints and adding Foreign Keys not only improves the quality of your database through ensuring referential integrity and data integrity in general, apparently it also helps the Query Analyzer design better plans!

Take a [...]

For some reason SQL Server doesn’t have an easy way to "Create TO" for database diagrams, unlike stored procedures, functions ,etc.

Here is how you can achieve moving a database diagram (or copying a database diagram) in SQL Server 2005

use Old_Database go –this will copy your database diagrams into a temporary table select * [...]

How to find out if a record exists in a table efficiently using the IF EXISTS keyword, and 2) How to test and optimize two queries to see which is faster using SQL Server Management Studio. Includes screenshots

The T-SQL aggregate functions (COUNT, SUM, AVG, MIN, and MAX) can all be used with the DISTINCT keyword to calculate them on distinct columns only.

How to search if a trigger contains certain text in SQL Server 2005:

SELECT OBJECT_NAME(id)
FROM syscomments
WHERE [text] LIKE ‘%your_search_here%’ AND OBJECTPROPERTY(id, ‘IsTrigger’) = 1
GROUP BY OBJECT_NAME(id)

When designing a database, and creating the tables and schema, we have to choose carefully what we want our primary key to be. There are many different aspects to this. This article discusses the benefits of using a GUID over an Integer primary key.

A power tip on increasing your query execution speed is to prefix your table and stored procedure names with dbo. By prefixing with dbo, Our database makes one less call. Normally, when you do not use the dbo keyword, on a query such as Select * from Users where UserID = @UserID, it will first check the user’s schema to see if that table exists for them.