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
- 270 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
Optimization..
yuppicide
Member Posts: 410
When I go to File, Database, Information, there's a button that says Tables. In there I see an Optimize button.
Besides the obvious, what does it do? Will it possibly help anything if I do them all?
I did two tests, one was at 95.something% and after optimization it's 97.something%. Another onr was at 85.something% and it's now 97.8%
Besides the obvious, what does it do? Will it possibly help anything if I do them all?
I did two tests, one was at 95.something% and after optimization it's 97.something%. Another onr was at 85.something% and it's now 97.8%
0
Comments
It will clean up blank spaces n such and reduce the database size used. There's been discussions on if it actually increases speed. It might but it's probably un noticable. I try to do it once a week.
http://www.BiloBeauty.com
http://www.autismspeaks.org
Native: because you create/modify/delete records, the indexes (stored in a B-tree) become fragmented and NAV balances the B-trees again for the indexes (making space the indexes use smaller). This makes that reading becomes faster, but writing becomes slower because there is no more place to insert new records. My advice is to do this ONLY for tables that change very little. So no sales lines, or item ledger entries. But yes for customer, vendor, item.
The only way to do this is manually or using some keylogging tool that sends the keys to the NAV-client (for NAV it still seems manual...).
SQL: It does a SQL index rebuild using the fillfactor of the table/index. It does NOT use the fill factor defined in the server properties. This value is only used when creating a table/index and if you don't specify a fillfactor. The fillfactor of a table/index can be changed by using the rebuild index command and specifying a new value.
In the versions until 5.0 without SP, it also does a cleanup of the 0-sift records (and in some versions that created some problems).
It is best not to do it through NAV, but do it by using the rebuild index of SQL (there is a maintenance plan you can use if you want). The cleanup of the 0-sift-records should not be necessary anymore because you should be on 5.0SP1 or later.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!