I only have one problem with this suggestion, why are you using uniqueidentifiers for your primary keys? This is bad, and here's why:

1. A uniqueidentifier is a lot larger than...

This sounds a lot like the CLR code that was killing our system. If you want, I can send you a solution in nothing but TSQL.

Don't be an enabler!!

It will create a unique clustered non-null index. A primary key must be non-null and must be unique, however, you can add the keyword nonclustered if you don't want it...

You have an IO bottleneck. Review your disk configuration. Specific to this problem, make sure that the backup is being written to a different drive than the log file, data...

It probably exists as a different owner than dbo such as: mylogin.Patient_Dem2

Add the following column to your table:

Alter Table dbo.WebLog Add ilogWritten As Cast(Convert(varchar, logWritten, 112) as int)

Then do this query:

Declare @istartDate int, @iendDate int

Select @istartDate = Cast(Convert(varchar, @startDate, 112) as...

Perhaps I'm not understanding the question, but the number of days between the last day of the month and the previous last day of the month is the day of...

Post one of the queries that is known to cause this problem.

Have you reviewed the query plan?

Are the log files on the same drive as the data files? What about...

Use sp_reassign_dtspackageowner to change the owner of the package to an existing owner.

I think Anders gave the best answer!! The only other plausible reason is that he's trying to make you look better by intentionally doing bad things.

The lead developer at my former company had downloaded some canned code off of some website that used the CLR to access the Windows API for time zone information which...

Adding on to what Tim said, I would leave the FK out of the Subcategories table. Otherwise, you'll have to add a Size subcategory for every category that has a...

SSIS has its own service entry. However, it is only needed for the creation of the maintenance plan, not for running it. In fact, starting with SP2, you don't even...

CLR is there to allow you to do what you can not do in T-SQL. You should always prefer T-SQL over CLR when you can because it performs better.

Perhaps in...