Viewing 15 posts - 11,386 through 11,400 (of 22,219 total)
Brandie Tarvin (1/19/2012)
I am beyond thrilled...
"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
January 19, 2012 at 5:52 am
SQLRNNR (1/18/2012)
L' Eomot Inversé (1/18/2012)
SQLRNNR (1/18/2012)
I have been able to...
"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
January 18, 2012 at 5:47 pm
TravisDBA (1/18/2012)
Grant Fritchey (1/18/2012)
"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
January 18, 2012 at 3:38 pm
The thing is, you can still use Profiler with all the cool stuff it does for you. It can generate TSQL for you to output trace events to a file,...
"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
January 18, 2012 at 3:21 pm
TravisDBA (1/18/2012)
TravisDBA (1/18/2012)
Dave Ballantyne (1/18/2012)
I still say that using SQL Profiler is a good place to start
It hasnt been said explicity in this thread , so i will 🙂
Never...
"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
January 18, 2012 at 3:04 pm
I would set up an extended events session to capture the queries being executed on the server. I would also start monitoring the server using Performance Monitor.
You need to...
"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
January 18, 2012 at 8:52 am
Cadavre (1/18/2012)
"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
January 18, 2012 at 8:13 am
Jan Van der Eecken (1/18/2012)
Jack Corbett (1/18/2012)
"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
January 18, 2012 at 7:24 am
Nope, no query that I saw either.
"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
January 18, 2012 at 4:35 am
You have to understand where the split occurs between what's useful to monitor and what's not. Memory & CPU monitoring is now different. You're not going to want to look...
"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
January 18, 2012 at 4:32 am
You're looking at a 500+ rows in a multi-statement UDF and you've got index hints inside the queries? I think you're digging a very deep hole. Hints should be used...
"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
January 18, 2012 at 4:15 am
Jeff Moden (1/17/2012)
Grant Fritchey (1/17/2012)
The thing is, some questions lend themselves to that style of...
"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
January 17, 2012 at 9:09 pm
Good to see you got the answer. Thanks Gianluca
"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
January 17, 2012 at 7:49 am
Simply joining the tables, yes, you're going to return two rows. So, what are the filter criteria that makes it so you'll only get one? Add that to a WHERE...
"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
January 17, 2012 at 6:18 am
I strongly recommend you DO NOT join the two views together. Joining one view to another or nesting views within each other leads to incredibly complex execution plans which can...
"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
January 17, 2012 at 5:49 am
Viewing 15 posts - 11,386 through 11,400 (of 22,219 total)