SQL PerformanceYou know, Microsoft has been putting out a steady stream of pretty cool articles. This one, shows some quantifiable data as it relates to disk partitioning. (Thanks to my buddy Marc for pointing this one out to me!)
Have you guys seen the new Performance Analysis with Logs (PAL) tool posted by Microsoft at codeplex for tuning any type of system using performance counters? It’s pretty amazing to say the least. Read more…
Hi again,
This undocumented command in TSQL reads your log file and returns results. If you’ve ever used a log reader such as the one from APEX, or any other log reader for that matter, you will see the resemblence. Here’s the syntax on how to call this particular function:
SELECT *
FROM ::fn_dblog(NULL, NULL)
Hi all, the following guide was taken from Microsoft’s best practices site. I’ve found out through the years that our product has been challenged by many of the performance problems listed in this guide, so it is definitely a good read!
You can find the Microsoft link here:
Here is the document for your reference as well: tshootperfprobs
Assuming you don’t have already have a fancy tool like Quest Software’s Performance Analyzer, or you aren’t using the Performance Dashboard offered by Microsoft, one way to quickly determine if you are CPU bound and what is actually utilizing your CPU utilization is to use a couple queries. I borrowed some information from the Microsoft document called Troubleshooting Performance Problems in SQL Server 2005 below. Read more…
