Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
neellotus
Starting Member
15 Posts |
Posted - 2012-09-03 : 11:44:20
|
Hi All,I am new to use Database Engine Tuning Advisor for tunning of my company's DataBase Named (ABCData) and I don't have any experience to Tuneup DB on my own. So i made trace template in SQL Profiler to find out slow Queries(those taking time more than 40 seconds to complete) and all data of trace storing in same Database(ABCData) Table named (Slow_Qrys). Then i run the trace for two days and it is sufficient time to cover workload.This trace showing 4 to 6 DB name in Database column of trace but i want to apply tunning only on DataBase Named (ABCData).Now i want to ask you, have anybody tunned your Whole DB and what is the result of this tunning, i mean after this tunning your DB performing fast transactions or not.Is your DB working fine?. And is it safe to run and apply all recommendations suggested by DTA of SQL 2005.Pls also tell me should i run whole DB Tunning or Run tunning on those tables & SP that are slow in resulting.Because i was read in google search that tunning whole DB is good than the tune only slow querys to overcome overlapping of indexes.I am very very tensed & under pressure to do this.Pleeeeeeeeeease help me and suggest some solutions what i do? I will be very thankull to you.ThanxRgrdsNeel |
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
Posted - 2012-09-04 : 01:39:18
|
It seems you have the list of queries. Go through them one by one - starting with the most used and tune the queries. Also, do you have a maintenance plan in place? Such as Index management , statistics etc?The Database Tuning Advisor promises much but can also lead to problems. No in-depth expertise is required, therefore tempting for non DBAs to run a sample workload. The Advisor typically recommends indexes and statistics. Do not just add them without considering the consequences , for example, a) Adding new indexes has an extra storage space requirement b) Extra maintenance is required . How will this impact the maintenance window? Jack Vamvas--------------------http://www.sqlserver-dba.com |
|
|
Ibid
Starting Member
4 Posts |
Posted - 2012-09-12 : 14:09:00
|
It is never safe to apply recommendations without properly testing them first, no matter what tool you use. I also think that including only the slow running queries isn't really a representative workload - because if by improving the performance of a relatively slow query you'll be degrading the performance of anohter query which runs twice as many times a day, overall your database performance will not improve at all.If you're looking for a tool to optimize the performance of the entire workload, you might want to try Qure Optimizer [url]http://www.dbsophic.com/qure-optimizer.html[/url]. It recommends indexes (create, alter and drop), SQL re-writes and schema changes, while benchmarking these recommendations to make sure there's no degredation. Of course, you should properly test these recommendations as well. |
|
|
|
|
|
|
|