Discussions
Activity
Best Of...
Sign In
·
Register
Home
›
SQL Performance
Howdy, Stranger!
It looks like you're new here. Sign in or register to get started.
Sign In
Register
Quick Links
Categories
Recent Discussions
Activity
Best Of...
Unanswered
Categories
All Categories
73
General
73
Announcements
66.6K
Microsoft Dynamics NAV
18.7K
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
310
Dynamics CRM
109
Dynamics GP
10
Dynamics SL
1.5K
Other
993
SQL General
384
SQL Performance
34
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
260
Feedback
12
NAV TechDays 2013 Sessions
13
NAV TechDays 2012 Sessions
NAV 2009/2013/2015/2016 on SQL2014 - Use Delayed Durability = FORCE or ALLOWED during data upgrade?
rsaritzky
Member
Posts:
469
2016-01-08
in
SQL Performance
Someone in another thread mentioned using Delayed Durability = FORCE or ALLOWED during data upgrades if the SQL Server is SQL2014. The article he referenced is:
http://sqlperformance.com/2014/04/io-subsystem/delayed-durability-in-sql-server-2014
If you do a demo install of NAV2016, Delayed Durability is set to "Disabled".
Has anyone experimented with this during database upgrades, particularly from NAV2009->NAV21xx? Aaron Bertrand's results (author of article mentioned) seem to indicate a substantial increase in SQL performance if this feature is turned on. I'm wondering if anyone in the NAV community has tried it yet.
Ron
Ron
0
Sign In
or
Register
to comment.