Datagrip blocks my application
Answered
I'm currently use the latest EAP version of Datagrip. I'm working on a .NET Application which uses a SQL-Server 2017 database. In development i use a locally installed developer edition of SQL-Server. With the current EAP build is have the effect, that i get a timeout from the database when i do a query in my application on a table which is opened in the database view. It seems that Datagrip holds a lock on the table. Before running the application i did a sort and select on the table. Transaction mode is set to Auto and Read Commited in Datagrip. I'm sure that i didn't have the problem before with the latest release of Datagrip.
Please sign in to leave a comment.
There is good topic how to check locks in MSSQL, please read and run queries suggested to see if this is really DataGrip holds locks or not. I've just checked on SQL Express 2019 and SSMS, even after importing and querying a lot of data in DG, all tables are still accessible in SSMS.
Hello Yuriy,
thank you for your hints. With the sql's from the stackoverflow answers i could check, that locking is not the problem. I found that the query runs very long (nearly 2 minutes) when it is called the first time. Each subsequent call to the view is much faster (i think because the result is cached). I have misinterpreted that DataGrip could cause the problem because i closed DataGrip each time before i rerun the application. So i will concentrate on optimizing the view on which the query is based.
Regards
Andreas