sql - uncommittable transaction is detected at the end of batch. the transaction is rolled back -
We are having problems with server migration. We have an application that is doing so much transactions, it is working fine on a database server. But when the same database is transferred to another server, we are facing the following error.
Server: message 3998, level 16, state1, line1
unintentional transaction is finally found back batch transaction rolled back Has happened.
The same database has been copied with all the data on another server. If we change the connection string to the old server then it is working fine.
Can someone give tips on this?
Whatever you think is a problem, where the record is acceptable in a database, but not the second. The suggestion differnces between two database structures (yes, I know they should be identical, but clearly they are not). Suspicious you will find differnce a data length between either a matching variation, a data type differnce, or both. Yoos can also have a table where the definition of identity is unavailable and thus it can not be included as it is a required field and the value is missing. It is easy to use the difference to compare tools like SQl.
Comments
Post a Comment