mika Posted September 1, 2017 Share Posted September 1, 2017 When user is waiting fairly time consuming SQL query to finish and application crashes (halts without a trace but that's a another problem) for some reason, database connection might leave table(s) locked. This will cause said table to be unreadable (without dirty read) until database server is restarted. I thought that any and all database connections will be disconnected and any possible locks will be released when application crashes but that doesn't seem to be case. Do any of you have any suggestions how to track down and solve this problem? Database backend is Microsoft SQL Server 2014 Express and I use FireDAC access it. uniGUI version is 1.0.0.1406 (Complete). // Mika Quote Link to comment Share on other sites More sharing options...
Administrators Farshad Mohajeri Posted September 1, 2017 Administrators Share Posted September 1, 2017 This seems to be a weird case. Under no circumstances one should be able to lock a table in such a way that will require a sql server restart Quote Link to comment Share on other sites More sharing options...
mika Posted September 1, 2017 Author Share Posted September 1, 2017 Yes. I totally agree. It shouldn't be possible. I'm pretty sure I must be overlooking something. I'll keep investigating. // Mika Quote Link to comment Share on other sites More sharing options...
zilav Posted September 4, 2017 Share Posted September 4, 2017 SET XACT_ABORT ON By default lost connection to SQL server does NOT considered an error to rollback open transactions and so affected tables stay locked. 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.