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
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 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
Options
NAV 2018 - Change Data Capture (CHANGE_TRACKING)
shei
Member Posts: 9
Hello everyone,
It seems MS activated CDC by default in NAV 2018 and did not documented why and if it's necessary. Couldn't find anything regarding this. According to Microsoft's CDC article, it is recommended to also activate SNAPSHOT_ISOLATION with CDC, which happens not to be active in NAV 2018 CRONUS databases.
What's the deal?
Reason why I am asking, a client of ours get sporadic Severity 16 warnings saying the automatic cleanup got blocked because of table xyz (different tables).
Thanks!
It seems MS activated CDC by default in NAV 2018 and did not documented why and if it's necessary. Couldn't find anything regarding this. According to Microsoft's CDC article, it is recommended to also activate SNAPSHOT_ISOLATION with CDC, which happens not to be active in NAV 2018 CRONUS databases.
What's the deal?
Reason why I am asking, a client of ours get sporadic Severity 16 warnings saying the automatic cleanup got blocked because of table xyz (different tables).
Thanks!
1