>We have some performance problems with SQL Server. using standard license, SQL Server version 2016, one user is running a report, during executing the query the other user is unable to save the record until the query if finished. This could be understandable if there are perhaps a lot of users and extreme slow queries running, but in this scenario it does not seem to make sense. An enterprise license may give us the possibility to lower the usage for the query, but this seems to be like killing birds with cannons. What else could be the reason for this behavior?

What is the isolation level and locking hints if any. Are you retrieving the data to a local cursor and freeing the connection or keeping it open for the life of the report?