Viewing 15 posts - 12,586 through 12,600 (of 22,224 total)
There is no criterial for a join between those tables. It looks like you want a LEFT JOIN, but without joining criteria (a foreign key), you can't make that happen.
"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 6, 2011 at 7:05 am
Brandie Tarvin (5/6/2011)
Editor's Note:
"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 6, 2011 at 6:52 am
Yes.
There is no "in general." It really depends on the situation and you should test your situation because different ones will work better under certain circumstances.
"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 6, 2011 at 5:10 am
Without using a 3rd party tool, nope. You have to restore the database somewhere and then retrieve the tables that way.
If you want to talk about possible 3rd party solutions,...
"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 6, 2011 at 5:09 am
It could be blocking, other processes running on the server causing the restore to slow down. Or, it could be that open transactions on your backup are being rolled forward...
"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 6, 2011 at 5:07 am
You should not be shrinking your files as a regular part of your operations. If you are, that's indication of problems somewhere. It does sound like you're in Full Recovery,...
"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 6, 2011 at 5:04 am
I'd look to see if there are blocks of some sort going on in production, but other than that, I'd want to see more data gathered. You said the servers...
"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 5, 2011 at 12:00 pm
I go with PowerShell and use remoting and then you can thread it and fire it on every server, all at the same time, no issues. Here's a small blog...
"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 5, 2011 at 11:54 am
There is no alternative tool. That's the best one.
You will absolutely need to plan for thorough testing. One of the issues we found early on when migrating to 2005, but...
"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 5, 2011 at 10:23 am
yes, the problems do occur in the engine, but they're very rare. If you're hitting them all over the place, then I'd suggest one of two things is true. 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
May 5, 2011 at 7:20 am
Nuts. I'm slow. Yes, the Upgrade Advisor is the best source for this information. It's the required first step to perform this kind of upgrade anyway. Follow Microsoft's documentation. It'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
May 5, 2011 at 5:42 am
It's possible you've hit a regression, a piece of code that worked well in 2000 but not so well in 2008. Usually this happens on code that is problematic 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
May 5, 2011 at 5:35 am
The traceflag puts a lot more information than that into the error log. You should be able to get the database id, the spid involved, the exact resources at 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 5, 2011 at 5:28 am
If updating the stats works, then are you updating stats in production? Is production on a different version of SQL Server? If so, it's possible that you're effectively performing an...
"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 5, 2011 at 5:26 am
The amount of work to DELETE your data down to 5% of the size of production is probably just as much work to INSERT data up to 5% of production....
"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 4, 2011 at 8:08 am
Viewing 15 posts - 12,586 through 12,600 (of 22,224 total)