Viewing 15 posts - 14,941 through 14,955 (of 22,227 total)
Well, pretty much, we start the SAN, get it online and tested, and then start up SQL Server. They are two, completely seperate operations and even managed by two completely...
"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
May 26, 2010 at 7:14 am
nadersam (5/26/2010)
Grant Fritchey (5/26/2010)
"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
May 26, 2010 at 7:12 am
Jeff Moden (5/25/2010)
Steve Jones - Editor (5/25/2010)
"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
May 26, 2010 at 7:09 am
Since you're working in 2005, I'd suggest, especially for targeted information like this, to use the dynamic management views to pull the execution plans and execution information directly from 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
May 26, 2010 at 7:02 am
I would suggest using connection pooling. As much as possible, reusing connections is the way to go because it reduces the amount of memory that connections take up (new memory...
"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
May 26, 2010 at 6:55 am
karthikeyan-444867 (5/26/2010)
If we have fake/surrogate key in a table, will the optimizer use 'Clustered seek' ? I believe it will use 'Clustered Scan'.
If you use the "fake" key in your...
"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
May 26, 2010 at 6:18 am
karthikeyan-444867 (5/26/2010)
GilaMonster (5/25/2010)
karthikeyan-444867 (5/25/2010)
I am sure we shouldn't create Clustered index/primary key on an IDENTITY column.
There's a big, massive, huge difference between not using an int identity for a 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
May 26, 2010 at 5:37 am
Identity gaps are only an issue if, for whatever reason, you're assuming a perfect chain of numbers. Don't make that assumption and the gap problem goes away. The idea is...
"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
May 26, 2010 at 5:31 am
Jeff Moden (5/25/2010)
Grant Fritchey (5/25/2010)
Jeff Moden (5/25/2010)
Grant Fritchey (5/25/2010)
"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
May 25, 2010 at 11:14 am
Sandy2704 (5/25/2010)
"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
May 25, 2010 at 9:23 am
Gianluca Sartori (5/25/2010)
Grant Fritchey (5/25/2010)
"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
May 25, 2010 at 9:18 am
Grant Fritchey (5/25/2010)
"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
May 25, 2010 at 9:12 am
Sandy2704 (5/25/2010)
How is it caused by the bad code???
Just to give one example, our developers wrote a piece of code that made every call to the database, three times. So...
"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
May 25, 2010 at 9:10 am
Jeff Moden (5/25/2010)
Grant Fritchey (5/25/2010)
"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
May 25, 2010 at 9:04 am
I haven't been posting here at the water cooler because, frankly, I was appalled at how many posts I had here. But I have to share this one because 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
May 25, 2010 at 9:02 am
Viewing 15 posts - 14,941 through 14,955 (of 22,227 total)