Which Raid Level is Right for Me?
Choosing the right raid level for SQL Server takes careful planning. For example, do you require high performance reading data, but not writing?
Choosing the right raid level for SQL Server takes careful planning. For example, do you require high performance reading data, but not writing?
There are three must read articles by Microsoft regarding the TempDB
Be sure to check them out!
I had the pleasure of meeting Greg Low recently, a Microsoft Certified Master. Greg is an amazingly intelligent individual, with all kinds of SQL Server experience. Greg has updated the Plan Caching paper originally written for SQL 2005, and made it relevant for SQL 2008. You can find that paper located here. I encourage you to read it, it is amazingly important for anyone doing performance tuning.
Been meaning to blog more, but yowsas, time flies by. Anyhoo, this link is great for determining the exact nature of a wait type, and what it means. Read more…
Wow, it’s been a while since I posted last, so let’s get right to it. Microsoft has an interesting read on this article concerning the TempDB.
You 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…
Hi again,
A few months back our firm decided that performance was enough of a problem for our product that we figured hiring a Microsoft consultant to come out would be a good idea. We learned a lot from the analyst, not so much in terms of things we didn’t already know, but really, useful tools to help make our performance tuning easier. Along with the Performance Dashboard, which I ultimately wrote an entire training manual on, Mr. Microsoft Guy also told us about DMV Stats. If you are already aware of this tool, please stop reading now. However, if you are interested in knowing what it is, check out this link…