SpDeleteOlderRecords and log size
Hello
We have database ~60 GB with 120 GB free disk space. I tried to make SpDeleteOlderRecords procedure to remove some old data, but it's impossible to process, cause log file going over 120 GB and make error
"The transaction log for database 'XXX' is full due to 'ACTIVE_TRANSACTION'.
I checked and found that the log file can't be bigger and provide error. Why during this procedure log exceeds database size TWO TIMES ?
Are they any other ways to remove older data from database?
-
Is this your BarTender System Database or your own data database? If the former there are various options in Administration Console that could help with this maintenance task
0 -
Hello there.
This will require a DBA to look at your current setup.
I'll be happy to help out, I have been working with databases and Bartender for many years.
You can contact me on anders@evikali.dk.Br
Anders Rolann0 -
Hi Peter
I tried with the Administration Console and by Run Maintenance task, but as you see in screenshot - the same situation - transaction log rise over 120 GB, and we have only 120 GB free space, so the task can't complete.
The database has almost 70 GB so it's smaller than the log.
Is there any solution for that?
0 -
You are logging a lot of print job and Integration data, do you need all that? If you look at the System Database tab you can adjust what is being logged as you may not need to log all the details.
0 -
Hi Peter
I deleted Integrations Data, but from what I see, they don't appear as database file size.
So I still have data in over 67 GB.
And I asked about WHY the maintenance tasks create such big log (which cause aborting task), not about structure of my data.
0
Iniciar sesión para dejar un comentario.
Comentarios
5 comentarios