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
- 304 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 for Job Ledger Entry ?
omerfaruk
Member Posts: 16
On NAV 2017 (16585) , I can see that there are date compression options for several ledger entry types ( including Cust. Ledg. Entry , Vend. Ledg, Entry, Gen. Ledg, Entry .Bank Ledg. Entry. etc) . However I couldn't find a way to date compress Job Ledger Entry records. ( also searched on Google ) . Do you know a way to do that?
0
Answers
I think it just creates a "summary entry" and deletes all the other entries.
You can try doing yourself for job ledg. entry:
-make a backup of the table
-clear all entries and make a "summary" entry with the actual value.
-Start with small projects and see how it looks like.
These routines originate from the very early days of NAV. Where NAV charged you based on allowed database size, and the cost of physical disk space was also rather high. Neither of these situations exist today.
well,
if you have years and years, maybe millions of records, I presume this affects to the performance, right?
I have work with NAV\BC for almost 25 years. Including several databases of several hundred GB and one that was well over 1 TB. I have never once used data compression (or deleting of data) to resolve a performance issue on a ledger table. I would consider it a very last option, at best.
On the other hand, I have seen incidents where data compression was run and created problems. I can't speak specifically to compressing Job Entry. But in general I tend to avoid these processes.