I run SQL 2000 as my backend for RMS. My database is only 65 megs, but the log file has grown to 67 gigs! I only have 75 available total and am about to run out. How do I shrink the logfile, or what can I do before I get stuck in a jam.
Thanks, Nick
I run SQL 2000 as my backend for RMS. My database is only 65 megs, but the log file has grown to 67 gigs! I only have 75 available total and am about to run out. How do I shrink the logfile, or what can I do before I get stuck in a jam.
Thanks, Nick
Run from query analyzer
BACKUP LOG { database_name | @database_name_var } { [ WITH { NO_LOG | TRUNCATE_ONLY } ] }
backup log mydatabase with truncate_only
Your database is corrupted.
Also, do you have UPS, such as by apc.com ? Problems in the power supply can cause your database to be come corrupted.
Natt
"Nick" wrote:
67 gb????? and how transactions?
antonio
Nevermind guys, I got it figured it out. I had the wrong database type set. it was set to FULL and I changed it to Simple and the log size shrunk down to 12 megs.
Thanks for try>> I run SQL 2000 as my backend for RMS. My database is only 65 megs, but >> the
The database is not corrupted, it just hasn't been backed up. SQL Server transaction logs just keep growing until the DB is backed up, at that point, the transactions are otherwise saved, so the log is truncated. This is all dependent on DB Settings as Natt found.
Natt, Since you're running SQL Server rather than MSDE, you may want to use Enterprise Manager to create a Backup Plan. This is a super simple way to perform preventive maintenance and robust backups of your databases. Check out SQL Server Books Online, or Enterprise Manager Help for more information. If you want to use a backup plan, switch back to FULL Backup Type.
My Apologies to Natt and Nick, whom I seem to have reversed in my post...
Have something to add? Share your thoughts — no account required.
Ask the community — no account required