Viewing 15 posts - 17,806 through 17,820 (of 22,219 total)
Something is holding a lock on your system. It could be a long running process or an uncommitted or unrolledback transaction. Try looking at sys.dm_os_waiting_tasks or sys.dm_tran_locks to see what'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
April 6, 2009 at 7:22 am
Don't use auto shrink. That's a major performance hit in most circumstances. If you've had some kind of over-sized transaction or error with the log backups or something that caused...
"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 6, 2009 at 7:13 am
That warning is pretty straight forward. Somewhere in the code a string is getting placed that's just too long.
Also, on a side note, instead of using @@IDENTITY, I'd suggest 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 6, 2009 at 7:09 am
San (4/6/2009)
Somehow I managed to install SQL2k5 with different instance name and logged using "machineName\instanceName". Now another problem is that, when I select " " option in SERVER NAME...
"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 6, 2009 at 7:03 am
I liked the podcast even more than the editorial.
I don't think you were only pointing at those asking questions when you suggested we needed to treat others as we...
"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 6, 2009 at 6:49 am
While that does allow a single procedure to act on multiple tables, you're still only getting a single table per insert statement. You're just rigging the insert statements to sort...
"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 5, 2009 at 3:03 pm
Limiting parallel execution only eliminates deadlocks if the deadlocks are being caused by parallel execution. There are plent of instance where it's not.
In addition to use MAXDOP on the 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
April 5, 2009 at 3:02 pm
Right! Time to bring in the HR department.
"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 4:35 pm
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
Viewing 15 posts - 17,806 through 17,820 (of 22,219 total)