|
We recently had an incident with a giant sql server log file (transaction log). From the documentation, the default in sql server is recovery mode full that keeps all transactions in the .ldf until the next backup, so that you can rebuild you .mdf file incrementally from a backup by "redoing" all past transactions. I'm not really sure this is useful : in your experience what is the use of keeping track of all past transactions? The ability to go back to a given point in time, by rolling back all transaction made after that time? Apart from this point, do you think there are other downsides with recovery mode simple? |
I'm not sure if such problem has something to do with DataObjects.Net, but i think no. Are you tried to ask this on stackoverflow.com ?
Yes you're right : you can read http://stackoverflow.com/questions/302310/microsoft-sql-server-what-does-it-mean-that-a-transaction-log-is-full for instance. I'm just asking for an advice here because I think Do.net team has a very good knowledge of SQL server. This is absolutely not an high priority support request ;)
Ok then, i just respond to your question if you mistakenly place question in wrong forum. And your right DO team has good knowledge of SQL server and they can help you if they found time to answer.