Hi, trying to research this and haven't found much info yet. A client called to say that they had lost a bunch of transactions that had been entered into a sql 2000 db via our custom vb/ado app. Coincidentally, the same day that the transactions disappeared, the server ran out of disk space. I would expect that this would cause the log to have all kinds of problems, but would have thought that the client would have received errors committing transactions eventually - which they say they didn't get. They fixed the space problem pretty quickly by removing some old files. Would the transaction log roll things out, or could things have been in memory and unable to commit due to the log not being able to grow? I haven't seen any documentation on what would happen in this situation, figured one of you would probably know.
Thanks!
Phil
Thanks!
Phil