Are there SqlExceptions which throw but commit their data anyway?
- by Jonn
I've recently encountered the error:
System.Data.SqlClient.SqlException:
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
on one of my windows services. It's supposed to retry after catching an Sql Exception, what I didn't expect was that it seemed like the data was still going through (I'm using an SqlBulkCopy btw) regardless of it throwing an exception. I've never encountered this scenario before.
I'd like to know if there are other scenarios where such a thing like this might happen, and if this thing is entirely possible at all in the first place?
PS. If anyone knows the error code to the above exception, that would help a great deal as well.