Howdy, Stranger!
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
- 305 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
Date Compression
philbert
Member Posts: 5
Morning All,
We are just about to begin migration to a new Navision solution from fin 2.6 and have decided the best policy will be to date compress everything in the Item Ledger Entry table up to year end 2003, and then port that across to the new Db. A suggestion has been made to remove/ disable all the keys that aren't needed during compression in order to speed things up..
Anyone know if this is a good idea or if it will work at all?
We are running 2.6 with a 110GB C/Side DB
Ta!
We are just about to begin migration to a new Navision solution from fin 2.6 and have decided the best policy will be to date compress everything in the Item Ledger Entry table up to year end 2003, and then port that across to the new Db. A suggestion has been made to remove/ disable all the keys that aren't needed during compression in order to speed things up..
Anyone know if this is a good idea or if it will work at all?
We are running 2.6 with a 110GB C/Side DB
Ta!
0
Comments
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.