Viewing 15 posts - 13,411 through 13,425 (of 22,232 total)
If you can't shrink those files it's because SQL Server is retaining the transaction information. That usually means replication, log shipping, or mirroring is active. That's where I'd focus 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
February 2, 2011 at 8:19 am
Are you passing it the same parameters? Are the ANSI settings the same between the app and SSMS?
"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
February 2, 2011 at 8:10 am
Try adding a file on a different drive to the database as a log file. That should give you enough space so that you can then truncate it.
Also, if 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
February 2, 2011 at 8:05 am
If you nest the transactions, start one that wraps both procedures and start a second that only wraps the second procedure, you can rollback the second transaction without rolling back...
"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
February 2, 2011 at 7:59 am
Raghavender (2/2/2011)
Grant Fritchey (2/1/2011)
"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
February 2, 2011 at 7:42 am
Balaji M R (2/2/2011)
When i try to do this, i am getting following errors.
1. "Transaction (Process ID 66) was...
"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
February 2, 2011 at 6:56 am
Nothing different than any other upgrade. Have good backups. Test on a non-production system first. Run your database through the upgrade advisor and do what it says if any issues...
"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
February 2, 2011 at 5:49 am
GilaMonster (2/2/2011)
Grant Fritchey (2/2/2011)
If you have anyone there helping you, task them immediately with getting your backups prepared for a restore operation.
Backups? What are backups?
sourav_1002001 (2/2/2011)
"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
February 2, 2011 at 5:11 am
GilaMonster (2/2/2011)
Grant Fritchey (2/2/2011)
Another reason you might not see a plan in cache was if it was a trivial plan, but that's not the case here.
In SQL 2005 even trivial...
"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
February 2, 2011 at 5:10 am
In addition to what the others have suggested, what about log shipping or mirroring?
"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
February 2, 2011 at 4:53 am
And, if you're only doing a full backup once a week, you might want to consider doing incremental backups nightly. Then you'll only have, at most 48 or so log...
"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
February 2, 2011 at 4:51 am
If you have anyone there helping you, task them immediately with getting your backups prepared for a restore operation. You might not be able to recover this, so you'll need...
"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
February 2, 2011 at 4:44 am
If I'm understanding the requirements correctly, I'd put the second procedure into a transaction with a TRY/CATCH block that will allow you to roll it back if there are errors....
"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
February 2, 2011 at 4:42 am
It's got to be something along the lines Gail suggests. I just ran through it and it creates a plan and stores it cache just fine.
Another reason you might...
"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
February 2, 2011 at 4:38 am
While I wrote my own code to defrag indexes (in the book, listed below), I really prefer Michelle Ufford's[/url] code. It works wonders.
"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
February 2, 2011 at 4:31 am
Viewing 15 posts - 13,411 through 13,425 (of 22,232 total)