Viewing 15 posts - 8,641 through 8,655 (of 22,219 total)
The optimizer will know that an index is unique and may use that as part of it's decision process when putting together the execution plan.
"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
March 19, 2014 at 4:06 am
The command you're looking for in T-SQL is called MERGE. Here's the Books Online entry on 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
March 19, 2014 at 4:05 am
sunil88_pal88 (3/18/2014)
There is one more thing I forget to tell that on development server ,everything is fine .Data is uploaded in almost 3 minutes, but on production 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
March 18, 2014 at 10:05 am
If you capture query metrics and the wait statistics from those queries at the same time, you can then correlate from wait statistics directly to queries. But, that's got 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
March 18, 2014 at 4:22 am
If WorkID is staying an identity column, then, you're guaranteed that the combination of WorkID and WorkDate are still identical because WorkID will always still be identical. But maybe I...
"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
March 18, 2014 at 4:17 am
If this is a one-time shrink after a major data clean up, it should be fine. You just want to avoid a situation where you're growing then shrinking the database...
"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
March 18, 2014 at 4:08 am
Snapshot isolation is great when you have a mix of exclusive locks and shared locks because it isolates them from each other. But this is a mix of exclusive locks....
"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
March 18, 2014 at 4:07 am
Blocked processes or resource contention on that one database. That's all it takes.
"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
March 18, 2014 at 4:01 am
I'm pretty sure disabling them in this case won't speed things along. Shrink is at a lower level and having the indexes in place is just another set of pages...
"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
March 18, 2014 at 4:00 am
Instead of trying to write your own script, I'd suggest using one that's already written. Michelle Ufford's script is available[/url] and works quite well. You can schedule it to run...
"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
March 18, 2014 at 3:58 am
Not per se. I have a general suggestion to bump it to 35. You can get more specific and query the plans in cache to get overall costs and then...
"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
March 17, 2014 at 12:34 pm
I think SQLBuddy hit the most important point. Backup all the indexes as scripts first. Dropping or adding an index is a pretty trivial event, but knowing exactly which index...
"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
March 17, 2014 at 11:41 am
I'd start by identifying what is holding the lock and why it's holding it. That would be priority one. Is it an uncommitted transaction? Can you commit it? Do you...
"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
March 17, 2014 at 10:37 am
The query above can do that. You just have to filter by the name if that's what you want.
"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
March 17, 2014 at 10:03 am
CK2 (3/17/2014)
rraza (3/15/2014)
A DBA accidentally dropped a critical highly transactional table in production. Walk me through the exact procedure to restore it without taking...
"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
March 17, 2014 at 7:39 am
Viewing 15 posts - 8,641 through 8,655 (of 22,219 total)