Viewing 15 posts - 17,821 through 17,835 (of 22,226 total)
Bob Hovious (4/3/2009)
Congratulations Grant!!and Gary....
Okay, have moved from the Son Of Thread to this one. Seems more appropriate somehow.
...... Congratulations on turning away from the Dark Side.
Thanks.
I'm actually...
"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
April 3, 2009 at 12:53 pm
Since your databases are already offline, you've got failed installs and failed uninstalls on the same server, manually digging out will take way too long. I'd suggest backing up any...
"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
April 3, 2009 at 9:30 am
You must mean really big tables.
But even then, the processing should be taking place on the server. I've seen things lock up when the data starts to come back from...
"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
April 3, 2009 at 9:00 am
Cool. Glad I could help a little.
"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
April 3, 2009 at 6:55 am
Just as a quick check, run sp_who2 to see what's happening on the server.
If you really can't figure stuff out from the suggestions so far, I'd look into checking on...
"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
April 3, 2009 at 6:52 am
You absolutely can do it and it will work fine. Just understand, you will see contention on resources between the two servers, especially as the load increases on them. Make...
"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
April 3, 2009 at 6:50 am
chris.stuart (4/3/2009)
"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
April 3, 2009 at 6:26 am
Yep. One at a time.
You can have a procedure that affects lots of tables, but that procedure will have individual statements for each table within 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
April 3, 2009 at 6:12 am
DISTINCT and GROUP BY are both methods of aggregating data. In general terms, neither is going to perform better than the other one.
In general practice, you need to structure...
"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
April 3, 2009 at 6:10 am
That is strange behavior. I've never seen anything like it. If you can, post the code. If it's huge, post it as an attachment.
Do you have lots of PRINT statements...
"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
April 3, 2009 at 6:06 am
Perry Whittle (4/2/2009)
"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
April 3, 2009 at 6:04 am
I'm not sure, I haven't used this myself, and I don't see anything in the documentation. One point, Books Online suggests using the dynamic management function sys.dm_io_virtual_file_stats instead of...
"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
April 2, 2009 at 6:25 am
Yeah, I've read those. I was never completely dependent on IO, but it sure made me second guess even how much I used it.
But Gail was write to call me...
"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
April 2, 2009 at 6:09 am
I've never tried achieving that kind of measure before. But, I will say that you shouldn't be surprised if there are lots of reads even on a system that 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
April 2, 2009 at 6:02 am
I think he's referring to the statistics being out of date or insufficiently sampled. Just because you have auto-stats turned on doesn't mean that all the statistics are getting updated...
"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
April 2, 2009 at 5:48 am
Viewing 15 posts - 17,821 through 17,835 (of 22,226 total)