Viewing 15 posts - 10,636 through 10,650 (of 22,224 total)
Disregarding the size of the databases, how many user connections does each have? What are the transaction rates? If there is more activity on one than the other, then you're...
"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 18, 2012 at 3:55 am
You can change the alert to capture 1222. Or you can add 1205 traceflag so you get both, but that makes for very messy error logs.
"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 18, 2012 at 3:54 am
And you're only ever taking the tail log backup in an emergency recovery situation anyway. Just take the backup and then use it as part of the recovery (if needed)....
"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 18, 2012 at 3:25 am
The only way you can have foreign key constraints in place and still have orphaned records is for the foreign keys to have been added using the NOCHECK option after...
"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 5:42 am
rodjkidd (7/17/2012)
Good to see you are still communicating fairly normally! I guess 6 sessions in two at SQL in the City just wasn't enough to push you over the edge....
"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 4:13 am
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
Viewing 15 posts - 10,636 through 10,650 (of 22,224 total)