• State Suggested Answer
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 27 subscribers
  • Views 8346 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SQL Locks

carl.fedak
over 6 years ago

Hello,

 

We are using MSSQL 2014, and RR 6.1.1.137.

Our database server has C (170GB), D (2.2 TB), E (360GB), F (5.6TB).

Currently all databases are set to simple recovery, and our schedule is set to 2 hours.

Unfortunately, at least once a day we have a period where our application (custom built .NET web app) throws a bunch of errors saying it cannot write to the database, we are getting locks.  These are happening only at scheduled backup times, and typically when that happens we have 2-3 retries of the backups.

This is, of course, causing client impact.

Our database is not particularly busy, I feel like maybe we are just doing something wrong or Rapid Recovery would never really work for live databases.  In which case I'm unsure how they could be selling it.

One suspicion, we do have some fairly long running transactions in the application.  These are not changeable at this time.  Could this be causing issues like I've mentioned where DB locks are occurring?

 

Looking for any tips at all.

Parents
  • 0 over 6 years ago
    The transactions that sometimes take a long time are user driven, so not something I can easily change.

    There’s nothing in the sql logs. But if those long transactions are running is that maybe it? Because if they’re writing data in one large transaction sql wouldn’t want to give up doing that to pause for a backup, as it’s considered one operation. These transactions can take half an hour sometimes I’m told.
Reply
  • 0 over 6 years ago
    The transactions that sometimes take a long time are user driven, so not something I can easily change.

    There’s nothing in the sql logs. But if those long transactions are running is that maybe it? Because if they’re writing data in one large transaction sql wouldn’t want to give up doing that to pause for a backup, as it’s considered one operation. These transactions can take half an hour sometimes I’m told.
Children
No Data