Viewing 15 posts - 18,991 through 19,005 (of 22,226 total)
Do you have access to a trace or, assuming it's not production, can you run Profiler against it?
Without more info, I'm flummoxed. Sorry.
"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
December 18, 2008 at 1:05 pm
You can simply restore the database backup from the 2000 machine to the 2005 machine. You can also detach the database files from the 2000 server and attach them (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
December 18, 2008 at 12:31 pm
Where are you planning on running it? On production? NO!!!!!! curse words removed.
On a sandbox or development server, sure.
If you make him owner of the database, he can run 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
December 18, 2008 at 12:06 pm
Hmmm. I'm still with my original thought. You had a high severity error.
Any chance other people are inserting to that global temp table at the same time?
"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
December 18, 2008 at 12:04 pm
Snorkel.
But seriously, Profiler might not give the answer. What if there's a problem with memory or tempdb or disk space and there are waits occurring because page latches or...
"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
December 18, 2008 at 11:59 am
actually, that query wouldn't work. It puts 32767 times the same drop statement for each database until it runs out of databases then it replicates null and since it's only...
"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
December 18, 2008 at 11:55 am
Check the error log. You might be generating an error of sufficiently high a severity that it's just dropping the connection.
"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
December 18, 2008 at 11:12 am
It'll still result in poor performance and recompiles. I still think the better approach is a wrapper proc calling x number of other procedures.
"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
December 18, 2008 at 11:09 am
I grew up on Redneck. I can mostly understand it, but I can't really speak it much any more (except the occasional y'all that comes out every now & 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
December 18, 2008 at 10:14 am
Ah, but other DMV's will capture the parameters, the execution plan, aggregate performance characteristics... And they all join together and all through TSQL 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
December 18, 2008 at 8:31 am
I just checked and, according to one my local Oracel DBA's, the situation is the same there, so I'm not sure what your Oracle guys are getting at.
"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
December 18, 2008 at 7:47 am
Ah, reading the entire article... what a concept.
"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
December 18, 2008 at 7:18 am
I thought your name was Carpal Tunnel? Now I'm so confused.
"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
December 18, 2008 at 6:57 am
Heck yeah.
I mean, did you ever see this before:
http://support.microsoft.com/kb/931279
Great. Something else to worry about.
"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
December 18, 2008 at 6:55 am
And make sure you have enough space on the disk.
You might have problems with the query you're running as well.
"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
December 18, 2008 at 6:54 am
Viewing 15 posts - 18,991 through 19,005 (of 22,226 total)