|
database
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Sporadic Behavior From ITWJust yesterday, I created a SQL trace and ran it on a server. I then saved the output as a SQL script. I started the ITW and it actually tuned the SQL script. Now this morning all of a sudden the ITW tells me the workload file does not contain any tunable queries!?!?! What the @!#$ So I created another trace that JUST captured RPC COMPLETED and SQL STATEMENT COMPLETED events. I ran this trace for fifteen minutes. The trace generated 5000 rows of output. I saved the output as a trace file. Again, when I run the ITW, I get the message saying there were no tunable queries in the workload. The funny thing is is that the same queries that are in the new file are some of the SAME ones that were in previous trace that worked just fine... Is ITW that touchy or am I just not getting it? In a sentence, I don't like it, don't trust it and don't use it.
I feel you are much better off analysing the queries on your tables and designing them analytically from the most queried fields and using the execution plan, Queries times and reporting times to determine what works best for you. But then again some people on here swear by it. Go figure. Yes, the exactly same thing happened to me a while ago. And I'm damned if I
know what made it go away, but it hasn't happened since. If it's any consolation - I don't remember ever intentionally trying to solve this problem, yet it's gone now. Have you tried restarting the service? Freeing up some space on the disk where SQL is installed? ML |
|||||||||||||||||||||||