May 13, 2002 at 3:16 pm
I am creating a database. I am restricting the Transaction Log file size to 500MB. I have Maintenance/Optimization Plans setup to run every 30 minutes. Periodically I still get a message saying my Transaction Log is full and needs backed up to free space.
How do I keep my transaction logs from even reaching that allocated limit?
Is there a stored procedure or something that I can use to, let's say keep the log from growing to 300MB of the 500MB allocated?
Colin
May 13, 2002 at 3:23 pm
I have tried resizing (making larger) the File Size of the transaction log. It only continued to grow. And giving me that message when it reached that ceiling.
Backing up transaction log with no integrity every 30 minutes.
May 13, 2002 at 3:26 pm
What version of SQL are you using?
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
May 13, 2002 at 3:28 pm
Sorry, SQL Server 2000
May 13, 2002 at 3:29 pm
The database right now is only about 50MB and growing.
May 13, 2002 at 3:45 pm
Integrity of the db or log?
I have no int for the Trans logs.
May 13, 2002 at 3:56 pm
ok great!
I have tape backups running regularly. And yes I will manually do it now. Then set a plan to backup once a day with int!
Thanks
May 13, 2002 at 4:22 pm
Looks like that was the answer! It has already dropped from 393MB to 91MB! THANK YOU!
These forums are awesome!!
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply