Transaction Log SQLServer Full after Checkout

[JBayona]

Hi, we have a  project in enterprise architect  controlled with SVN Repository and the model project is stored in a database using Microsoft SQLServer 2008 R2, the packages in this project are very large(XML files with 8MB size or more) we have a problem when we try to  checkout  a package, We got the next message.

"Microsoft OLE DB Provider for SQL Server [-2147217900]

The transaction log for database 'MyDatabase' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases"

Searching in Microsoft Forums and checking in the database as the message suggest,  this problem happens  because the transaction is too long for the space in hard drive wich is dedicated to transaction log in the SQLServer Database. A possible solution is check the AutoGrowth option in the log configuration, but we have limited  resources and we can't allow this solution.

We would be really thankful with any help. The System Configuration is below.

EA Version: 9.2

Database Configuration:

Microsoft SQLServer 2008 R2
Recovery Model: Simple

[qwerty]

Well, I'd go to the DBA and ask to increase the transaction log.

q.

[JBayona]

Yes,  sorry for not mention it before, we tried it, but that just solved the problem until a transaction required more space, and we have to determine the exactly size  because the policies in DBA are very strict and we don't know how to calculate this size because the project can increase in the future. Maybe we thought there was a solution  directly in the configuration of EA.

[qwerty]

Never heard of such a thing. You should contact Sparx support directly via priority support.

q.

[Eve]

While I'm not a DB expert, I'd recommend disabling the option on the XMI import dialog to import using a single transaction.

Without having that there is no limit on transaction size.

Another thing to check is ensuring that you are using the "Save nested version controlled packages to stubs only" option. And that you version control each package. It will mean that each vc operation is smaller, faster and you encounter less locking management issues.

[JBayona]

Thanks Simon, I tried disabling the option 'using a single transaction' and it worked for the import, I would also like to know if there is a similar option in the svn configuration.

Furthermore We are reviewing our strategy in order to implement the "Save nested version controlled packages to stubs only" option as you suggested.