Viewing 15 posts - 10,636 through 10,650 (of 22,219 total)
And remember, foreign keys don't just act as a mechanism for preventing orphaned users. They also enhance performance (as long as they're enforced).
"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
July 17, 2012 at 3:52 am
L' Eomot Inversé (7/15/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
July 16, 2012 at 2:07 am
Evil Kraig F (7/12/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
July 16, 2012 at 2:05 am
rodjkidd (7/12/2012)
David Sutcliffe and Grant Finchley - he's not that scary in person you know... Just don't tell him that!
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
July 12, 2012 at 6:45 am
The single best source for understanding how to deal with wait states is this excellent white paper from Microsoft. It should answer most of your questions in detail.
In a nutshell,...
"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
July 11, 2012 at 7:52 am
Divine Flame (7/11/2012)
I don't find DTA very useful. If we want to get the missing index recommendations, DMVs (such as sys.dm_db_missing_index_details) are more helpful.
And the missing index information is not...
"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
July 11, 2012 at 7:37 am
chumphrey 12211 (7/10/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
July 10, 2012 at 10:27 am
Nope. SQL Server doesn't store versioned information about the objects inside of it. There's no way to get that directly. My recommendation, put all your database T-SQL code into source...
"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
July 10, 2012 at 3:28 am
Based on the names of the objects in your query, I'm assuming you're doing JOINS against views, not tables. That means any one view could actually be hitting multiple other...
"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
July 10, 2012 at 2:55 am
Golfer22 (7/9/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
July 10, 2012 at 2:50 am
Yeah, don't use profiler.
Instead, use trace events which are all done in T-SQL code. It's pretty easy. Here's an article on how to do it[/url].
However, since you're working 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
July 10, 2012 at 2:44 am
if the transaction logs grew because the databases were in full recovery without a log backup, I'd say, yes, go ahead and do a shrink on them. Otherewise, they've grown...
"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
July 10, 2012 at 2:33 am
It's basically using 'a' as it's starting point and bringing back anything that is greater than 'a'. That includes anything starting with 'a' but adding extra letters, so 'aa', 'aaa',...
"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
July 10, 2012 at 2:31 am
From all the tests and production work I've done with compressed backups, the only down-side is a very minor increase in CPU usage during the backup or restore process. The...
"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
July 10, 2012 at 2:28 am
The reason for this is that IN is effectively a series of OR statements checking for equality. Nothing equals NULL, so that data will never be returned. The 2nd post's...
"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
July 9, 2012 at 8:51 am
Viewing 15 posts - 10,636 through 10,650 (of 22,219 total)