Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Will SQL Diff backup lock table?
allenyyzhou
Member Posts: 142
Recently, we faced a problem with sql diff backup. Our client is using NAV 2013 R2, we take sql diff backup everynight, sometimes some users still use NAV at that timing, so there will be table lock happens and the NAV Instance just restart automatically. We asked Microsoft, they said this is normal because sql backup will lock table. Just want to confirm here in Mibuso, does anyone faced the same problem before?
0
Best Answer
-
Phenno
Member Posts: 630
As far as I know no, backups do not produce locks on any level. You can check more info here: http://www.sqlskills.com/blogs/paul/a-sql-server-dba-myth-a-day-3030-backup-myths/
But, backups can make load on server which will produce slower executions of some procedures executed from NAV (or elsewhere) that do make locks which, in turn, will last longer than usually.5
Answers
But, backups can make load on server which will produce slower executions of some procedures executed from NAV (or elsewhere) that do make locks which, in turn, will last longer than usually.
I think I agree with you, backup should not cause deadlock. Last week I updated CU to the latest one, maybe that will solve my problem.