The following is what led me to believe that the log would not grow due to the open transaction: There is plenty of disk space, we have the log in simple logging mode and have backed up the log prior to kicking off the process. ![]() If anyone is interested, the process is an organisation import in Microsoft Dynamics CRM 4.0. The process runs for several hours so it's not easy to play trial and error. I have attempted to prevent this by increasing the size of the transaction log file in the database properties, but I get the same error. So the process fails with the error "The transaction log for database 'xxx' is full". ![]() I have no control over the way this is executed.īecause a transaction is held open for the full duration, when the transaction log fills, SQL Server cannot increase the size of the log file. I have a long running process that holds open a transaction for the full duration.
0 Comments
Leave a Reply. |