simple package fails with The transaction log for database 'X' is full due to 'ACTIVE_TRANSACTION
0
votes
1
answer
58
views
I am not a DBA and our DBA has quit and now I have to try to figure out DBA issues.
So I am trying to create a job that deletes certain rows from a table and then uploads a set of new rows onto it from ODBC "Snowflake" for Athena, no truncation involved bc I do not want to truncate the whole table.
The package fails in both VS and SSMS and it gives the following error:
[Execute SQL Task] Error: Executing the query "QUERY" failed with the following error: "The transaction log for database 'X' is full due to 'ACTIVE_TRANSACTION'.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Since the package has 2 tasks and it kept failing on the first one which is the delete query, I thought maybe I needed to change the first task from running a query to executing a SP, that did not work. I read up on the error and some ppl said I might have to reboot the VM, that did not work. I saw some other solutions like shrinking the log files but I also read that that could cause issues with the data, which I would like to avoid. I saw I could increase the size of the log file but IDK how to do that nor if it will mess up the data like shrinking has the possibility to do. I also read that best practice is to find what is causing the log to fill up and try to fix the problem by optimizing it but I have no remote idea how to even start doing that.
Any advise ya'll can give?
Asked by Gianpiero Loli
(1 rep)
Jun 4, 2025, 06:30 PM
Last activity: Jun 4, 2025, 10:04 PM
Last activity: Jun 4, 2025, 10:04 PM