As you probably already know, SQL Server is very good at tuning itself. It has the ability to monitor itself, and through a feedback loop, it knows how to internally adjust and tune itself so that ... [Read Full Article]
As a rule of thumb, every table should have a clustered index. Generally, but not always, the clustered index should be on a column that monotonically increases--such ... [Read Full Article]
All the tips provided on this website about indexing are general guidelines. As with any general guideline, there are exceptions. Because of this, it is a good ... [Read Full Article]
When your transaction log grows large and you want a quick way to shrink it, try this option. Change the database recovery mode of the database you want to shrink from “full” to "simple," then truncate ... [Read Full Article]
Hints can be used with indexed views if you find that the Query Optimizer has not chosen the ideal index for best performance. Normally, if the following ... [Read Full Article]
If you need to implement cascading referential integrity (such as cascading deletes) in your SQL databases, use the cascading referential integrity constraint instead of triggers to perform the cascading ... [Read Full Article]
Because service packs include fixes that often affect performance (among other things) you should upgrade your SQL Servers with the most recent service pack when it becomes available.
If your SQL Server's tempdb database is heavily used by your application(s), consider locating it on an array of its own (such as RAID 1 or RAID 10). This ... [Read Full Article]
If your application needs to access views often, consider adding a unique clustered index to your views to significantly improve performance. When a view is created with a unique ... [Read Full Article]
While user defined functions can offer great convenience, they can also sometimes hurt performance. This problem with them is that they use row-by-row processing, similar to how ... [Read Full Article]