Viewing 15 posts - 7,366 through 7,380 (of 22,219 total)
I don't know of any mechanism of code enforcement at the server that you could do to make this happen. Sorry.
"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
October 16, 2014 at 4:19 am
It must be a hash of some kind based on the server. I got different values than you did. And, if I dropped the table and recreated it, I got...
"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
October 16, 2014 at 4:18 am
The size of the indexes is much more of a question than the number of them.
"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
October 16, 2014 at 4:10 am
TheSQLGuru (10/15/2014)
Grant Fritchey (10/15/2014)
TheSQLGuru (10/15/2014)
GilaMonster (10/15/2014)
TheSQLGuru (10/15/2014)
A proper profiler-to-local-disk script can be run to capture heavy CPU users with very little overhead on the system.
And an extended events session...
"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
October 15, 2014 at 12:18 pm
What he said.
And, you know where to go if you get stuck.
"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
October 15, 2014 at 11:20 am
BOR15K (10/15/2014)
I have created Countries_View and placed the problematic CASE within the view and then JOINT Cities A table with Countries_View B
and all works like...
"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
October 15, 2014 at 11:07 am
TheSQLGuru (10/15/2014)
GilaMonster (10/15/2014)
TheSQLGuru (10/15/2014)
A proper profiler-to-local-disk script can be run to capture heavy CPU users with very little overhead on the system.
And an extended events session will have even...
"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
October 15, 2014 at 11:03 am
Use extended events because they're much lower cost than trace (much, much, much lower). Capture rpc_complete and sql_batch_complete. That can show you which queries are running to completion and what...
"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
October 15, 2014 at 8:02 am
sql-lover (10/15/2014)
Grant Fritchey (10/15/2014)
That's one piece of functionality that didn't make the transition into the GUI for extended events. You just can't do it.
Thanks for reply Grant.
Wow, that was useful....
"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
October 15, 2014 at 8:00 am
There really are lots and lots of good books out there. I'd suggest getting a copy of Itzik Ben Gan's "Inside T-SQL Querying." It's a must read. You also can'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
October 15, 2014 at 7:52 am
If the transaction log was filled by these deletes, you might be better off breaking them apart and calling them separately.
"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
October 15, 2014 at 7:50 am
While you might have seen a minor improvement with forcing an index, that's a very bad choice most of the time for tuning. Let the optimizer do it's job. 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
October 15, 2014 at 5:01 am
You can't highlight part of a procedure and run it as if you were running the procedure. You have to build the procedure and then execute it to test it.
"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
October 15, 2014 at 4:59 am
It had to have gotten into cache the same way as all other plans. It was called and compiled that way. You'd want to look at the first operator in...
"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
October 15, 2014 at 4:53 am
If you're out of the period, there's not really any way to know what was happening without having set up the extended events ahead of time, or turning it on...
"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
October 15, 2014 at 4:47 am
Viewing 15 posts - 7,366 through 7,380 (of 22,219 total)