Query Plans – Who Needs Them
A while back I wrote about Query Plans asking the question “How Much Do You Need to Know About Query Plans?”
I’m curious who is taking the time to use this powerful tool?
For example, as a SharePoint administrator, do you find yourself having to optimize queries?
Are you an accidental DBA finding that you need to tune queries in order to keep the lights on?
Are you responsible for the operations of your database servers, and if so, what kind of use do you make of Query Plans?
Query plans are also used by Database Developers to optimize software they are developing.
Are you aware that you can use SQL Server Profiler to capture a text version of query plans as queries are being run? This can help you capture the plan of queries are they are executed real time. Note: be careful in that this process may place a heavy load on your server.
A few people have written in response to the previous Newsletter.
Sandro:
I am a developer and i have choose to focus on .Net development since 2008. As such i use to develop with SQL SERVER as my database system.
But i am not a database administrator and i have no idea about queries performance and the corellates.
I wish to have a lot of advises from you if you don’t mind.
Ken:
I would love to see detailed info on interpreting SQL “execution plan” results. I know what a “table scan” and a couple other basic things are, but I am only guessing about the meaning of some of the other things that show up.
Here are a couple links providing you with a lot more detailed information about how to use a Query Plan.
How to use a SQL Server Plan Guide to Tune Queries
Execution Plan Analysis
Why not write in and share how you use Query Plans in your job? Let us know what role you are performing (mainly) and how Query Plans assist you in doing your job better. Send your notes or comments to btaylor@sswug.org.
Cheers,
Ben
$$SWYNK$$
Featured White Paper(s)
Hybrid Management White Paper
Written by AvePoint
As organizations worldwide continue to look for ways to… (read more)