SQL DB Full
Hi,
I have Bartender Automation 2016 R6 installed on one of my computer. This has been active since Feb 2022 and has been recording print jobs since then. Off lately, I realized that my DB maintenance setups don't help to free space in DB and is creating backup files of full DB. As a result, my DB has reached its maximum capacity i.e. 10GB and I can no longer record new print jobs.
Can someone help, please?
-
Hello Samson,
Welcome to the BarTender Community Forums.
I am sorry to hear that your database seems to be filling up with logs. I wanted to ask a few questions based on the information we have to see if we can come up with a solution. Can you open the BarTender Administration Console and open the Administrative tasks tab?
- Can you send me a screenshot of what comes up when you click "View Database Size"?
- Can you successfully Run Maintenance? If not, could you send us a screenshot of the error message if there is any?
Thank you in advance.
0 - Can you send me a screenshot of what comes up when you click "View Database Size"?
-
Hello Xabier,
Thanks for coming back.
please see below images,
1. DB size snapshot
2. The auto-run of maintenace service has stopped now. The last .bak was created on 22-12-2022 after which it stopped(probably because the DB is full now). If I click 'Run Maintenance' or 'Purge all records now', I see a message 'Maintenance task is currently running, please try again later' .
0 -
Thank you for the information Samson.
You may need to use SSMS to manually run a maintenance procedure on your system database. The SQL Maintenance procedure for the system database is outlined in this help file. If you can run that, it should fix the problem. The amount of logging under the System Database and Print Job Logging tabs, or a shorter maintenance interval, can then be adjusted to keep the database from getting too large. Here are the usual steps:- In SQL Server Management Studio, right-click on the BarTender system database (SystemDB1) -> click properties -> go to files. For the transaction log under the autogrowth/maxsize column, click the ... button. Set the max file size to unlimited.
- Then still in the system database properties->go to options->set the recovery model to Simple.
- Run the "manual unlock" procedure to unlock maintenance, if necessary (see below).
- Start the Administration Console to run maintenance.
- Once maintenance is complete, take a look at the Transaction Log file to see how much it's grown.
- Go back into database properties and set the size limit of the file to be somewhere in the magnitude of the size of the file on disk, instead of unlimited.
- Previous versions of this help file mentioned a truncate command to truncate the entire database. Do not use a truncate command as this ruins the backup chain. This feature has been deprecated since before 2010. Instead, try one of the options in the next section to help reduce the database size.
Hopefully, this will do away with the issue. Let us know if it helped!
0 - In SQL Server Management Studio, right-click on the BarTender system database (SystemDB1) -> click properties -> go to files. For the transaction log under the autogrowth/maxsize column, click the ... button. Set the max file size to unlimited.
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
3 Kommentare