K2 Database Transaction Log


Badge +10

I am consideng switching the K2 database mode to "Simple". This is mainly because of performance issues and the transaction log file getting too big. I have tried setting a limit on the transaction log fie to about 2GB but I have been getting transaction log is full error when doing any function that interacts with the K2 database such as editing a form or refreshing a service object. For some reason the transaction log is not being reused when it is full. I would not have thought that refreshing a service object would take up 2 gb worth of transaction log space. This is my development machine so I am not too worried about point in time recovery  The database is backed up daily. Back to the point, I wanted to know ,however unlikely, if there are any K2 features that would not work when switiching the K2 database to simple mode.

 

Thanks

 


3 replies

Badge +2

As far as I know there should not be any K2 features that would be affected but make sure to take full backups regularly because with simple mode the most recent backup are unprotected. In the event of a disaster, those changes must be redone!!! 


 


http://msdn.microsoft.com/en-us/library/ms189275.aspx


 


http://help.k2.com/helppages/k2blackpearlGettingStarted4.6.4/Disaster_Recovery_Introduction.html

Badge +10

Great. Thanks Kevin

Userlevel 1
Badge +3

The transaction log grows rapidly when developing smartforms, we had the same issue. For our development environment we switched the backup mode to simple. Didn't experience any problems.

Reply