Viewing 15 posts - 12,301 through 12,315 (of 22,224 total)
In a perfect world, 15% is probably workable, but with unexpected data loads, badly performing apps, failed maintenance jobs, sunspots, alien invasion... I prefer to run 30% free, minimum, unless...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 15, 2011 at 5:30 am
If a query is executing, it has an execution plan. The plan comes first. And it gets stored in the plan cache prior to execution as well. If that process...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 15, 2011 at 5:26 am
Looks like parallelism might be getting you. The cost for the plan is only 3. What is your cost threshold for parallelism? Default should be 5. Try setting it up...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 15, 2011 at 4:58 am
Instead of checking the error log every two hours, why don't you just have the errors forwarded to you directly. Then you know about them when they happened rather than...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 15, 2011 at 4:51 am
The thing is, it's likely to reduce deadlocks, but it's unlikely to eliminate them and it certainly won't prevent them in the future. Best way to avoid or fix deadlocks...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 14, 2011 at 4:07 pm
Stefan Krzywicki (6/14/2011)
Grant Fritchey (6/14/2011)
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 14, 2011 at 12:31 pm
Perfmon is extremely lightweight if you're capturing the data out to a file other than the OS drive or on of the data or log drives for the database. If...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 14, 2011 at 12:03 pm
Oh yes, there's a whole elite level of forums where we actually post only real answers instead of the usual pile of... oh my god... ninjas... arggghhhh!!!!
Nothing to see here....
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 14, 2011 at 10:39 am
I wouldn't get too hung on trying to correlate the two, but the events are showing pages read. A 1 is one page. 2, etc. are more pages. I don't...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 14, 2011 at 10:37 am
Profiler is for viewing the results of and defining server side traces. You can also run it directly against a database to capture data, but I don't recommend it.
It's primary...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 14, 2011 at 10:27 am
opc.three (6/14/2011)
The StatementSetOptions in the XML are apparently wrong per this bug report:
The bug report is for one of the 2008 CTPs but the bug is there in my...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 14, 2011 at 10:24 am
Yep, that would do it.
You may also have to drop individual database users as well, especially if that login created objects out on the databases with itself as owner.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 14, 2011 at 9:41 am
So, do I understand correctly, the shutdown was taking a long time or was hung? Did you just power off? Sounds like it was trying to deal with an open...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 14, 2011 at 9:40 am
Was the reboot in response to a problem or was it a clean shut down because of a service pack or something? If you shut down because of a hung...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 14, 2011 at 8:29 am
Without seeing both execution plans, we're just guessing.
Let's speculate for a moment. Maybe, you're getting timeouts on the optimizer. Adding a nonclustered index changed the order in which plans were...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 14, 2011 at 7:31 am
Viewing 15 posts - 12,301 through 12,315 (of 22,224 total)