March 13, 2019 at 11:53 am
Hi all,
I am an accidental DBA that has been assigned to monitor and optimize the database (SQL Server 2016).
I am receiving the below error an is not clear to me how to fix it
In fact it has occurred only two times till now while there were some long running jobs that blocked each other (an update in the table from a Agent job and a select in the same table from a SSRS report).
The update uses also e xp_cmdshell that remains open during all the time.
The recovery model of the database is simple and i do not see any problem with the available space in the server.
Please can anyone help me with this issue or just direct me to the appropriate direction to further investigate.
Thank you
Orni
March 18, 2019 at 2:01 pm
Review the following URL, it may provide some guidance (copy and paste the url into a browser):
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/fea1c821-5092-4e32-8559-f695d6a83a76/sql-server-2014-transaction-log-for-database-is-full-due-to-activetransaction-error?forum=sqldatabaseengine
March 19, 2019 at 5:44 pm
Orni - Wednesday, March 13, 2019 11:53 AMHi all,
I am an accidental DBA that has been assigned to monitor and optimize the database (SQL Server 2016).
I am receiving the below error an is not clear to me how to fix it- The transaction log for database '' is full due to 'ACTIVE_TRANSACTION'
In fact it has occurred only two times till now while there were some long running jobs that blocked each other (an update in the table from a Agent job and a select in the same table from a SSRS report).
The update uses also e xp_cmdshell that remains open during all the time.The recovery model of the database is simple and i do not see any problem with the available space in the server.
Please can anyone help me with this issue or just direct me to the appropriate direction to further investigate.Thank you
Orni
Another thing to check is that it could be that the log has a max size set and you have reached that limit. You can execute sp_helpfile in the database to see the files, max size, growth settings. Or in SSMS, right click on the database, select properties and select Files for the page on the left. Then you can view the same properties.
Sue
March 20, 2019 at 9:58 am
I have been getting those messages at the QA and Development instances and its like Sue_H said, check your log size, when its full that's the message it will throw.
Change the max size.
March 20, 2019 at 6:16 pm
Orni - Wednesday, March 13, 2019 11:53 AMHi all,
I am an accidental DBA that has been assigned to monitor and optimize the database (SQL Server 2016).
I am receiving the below error an is not clear to me how to fix it- The transaction log for database '' is full due to 'ACTIVE_TRANSACTION'
In fact it has occurred only two times till now while there were some long running jobs that blocked each other (an update in the table from a Agent job and a select in the same table from a SSRS report).
The update uses also e xp_cmdshell that remains open during all the time.The recovery model of the database is simple and i do not see any problem with the available space in the server.
Please can anyone help me with this issue or just direct me to the appropriate direction to further investigate.Thank you
Orni
How big is the log file in question?
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply