Viewing 15 posts - 8,071 through 8,085 (of 22,219 total)
I'd also suggest checking the error logs to see if you can tell why the database is offline.
"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, 2014 at 1:44 am
ramana3327 (5/25/2014)
One more doubt. Suppose if I have 2 indexes on a table with almost with similar columns. How can we find which index needs to drop and which...
"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, 2014 at 1:32 pm
You have to have a page file. So yeah, you're going to have it. Size and location are the only discussion points.
"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, 2014 at 5:38 am
Development should be the path to production, so yes, everything you're going to do on production should be done on development first.
And never, ever trust the DTA. Test everything 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, 2014 at 4:04 am
On the 50 ms of savings before you apply an index, Let's say we have an index that runs in 30ms. Does it need an index if we can shave...
"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, 2014 at 4:02 am
Disks are disks, even in most virtual environments. Stacking everything into a single location absolutely leads to a bottleneck.
"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, 2014 at 4:00 am
Eugene Elutin (5/23/2014)
... SQL Server doesn't really support code reuse in a useful way...
I would say that it's very arguable statement...
😉
And I am more than willing to have that discussion....
"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 24, 2014 at 7:08 am
Ed Wagner (5/23/2014)
Grant Fritchey (5/23/2014)
BWFC (5/23/2014)
"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 23, 2014 at 8:10 am
Write two queries. SQL Server doesn't really support code reuse in a useful way. If you have two different sets of requirements, write two different queries.
"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 23, 2014 at 8:01 am
Joining view to view like that is a very common code smell that can lead to serious performance issues. In most cases you're much better off querying the data directly...
"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 23, 2014 at 7:57 am
I'd also suggest going with the schema.
Or, if you have to name the tables, I'd go with naming them MyTableStaging or something like that instead of using old school Hungarian...
"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 23, 2014 at 7:52 am
That would be a job, if you have one, that is scheduled, by you the DBAs, to rebuild indexes to remove their fragmentation.
"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 23, 2014 at 7:50 am
BWFC (5/23/2014)
"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 23, 2014 at 7:31 am
srikantmeister (5/21/2014)
also try tuning adviser recommendation for whatever query...
"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 22, 2014 at 6:58 am
Maybe there's been a recent data removal. That would shrink the size of the backups.
"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 21, 2014 at 1:08 pm
Viewing 15 posts - 8,071 through 8,085 (of 22,219 total)