Access your Pro+ Content below.
The most dangerous game: Hunting down bad SQL query performance
This article is part of the SQL Server Insider issue of July 2011, Vol. 6
Once you’ve fine-tuned your databases’ indexes, maxed out your hardware and gotten the fastest disks money can buy, you’ll hit a limit on how much performance you can squeeze from your SQL Server machines. At some point you have to focus on fine-tuning the applications rather than beefing up SQL Server itself. That takes you into the somewhat tricky world of query analysis, where you try to identify database queries that -- because of the way they are written --aren’t performing as well as they could be. SQL Server comes with an excellent tool, SQL Profiler, that’s designed to capture traces. Think of these as similar to a network packet capture: You’re actually capturing the raw queries being fed to SQL Server, along with information about their execution time. Using this raw data, you can spot bad SQL query performance, and then offer advice to the application developers on how to improve them. Actually improving performance does depend on the ability to change the applications themselves, so this isn’t often an option for ...
Access this PRO+ Content for Free!
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
Features in this issue
As independent software vendors begin to roll out core business systems on Microsoft SQL Azure cloud service, larger enterprises are slower to migrate.
SQL Server is faster when the queries behind your applications are faster. Learn how to spot bad SQL query performance, and then work with developers so you can improve throughput.
News in this issue
Virtualization promises big savings for businesses, and few are decrying its influence. But is it always the answer? Are there SQL Server virtualization risks to learn about first?