Analysis View: s-l-o-w update on SQL Server 2000

jbech
Member Posts: 2
One of my clients (running Navision Attain 3.60 on SQL Server 2000) reported extremely slow update of their analysis view after adding a new dimension. Their database contains only some 90,000 G/L Entries but after adding the new dimension code and confirmed deletion of existing analysis views, a renewed update took roughly 20 hours (speed: 1 record/sec)!
I have made tests on a local SQL Server based on a Navision Backup from the client. This revealed that updating G/L Entries ran as expected but when it came to G/L Budget entries, the speed slowed down to 2 records/sec.
Tests on a native Navision Attain ran smoothly so the problem is exclusively related to SQL Server.
We have tried updating stats, recreating indexes and truncating the transaction log with no apparent effect.
Any hints would be greatly appreciated.
I have made tests on a local SQL Server based on a Navision Backup from the client. This revealed that updating G/L Entries ran as expected but when it came to G/L Budget entries, the speed slowed down to 2 records/sec.
Tests on a native Navision Attain ran smoothly so the problem is exclusively related to SQL Server.
We have tried updating stats, recreating indexes and truncating the transaction log with no apparent effect.
Any hints would be greatly appreciated.
0
Comments
-
Tables :
-365:"Analysis View Entry"
-366:"Analysis View Budget Entry"
You need to maintain less SIFTLevels on the tables:
Try keeping only levels on the following levels:
-the level ending with "Posting Date",
-the level ending with "Dimension 4 Code" (dimension 3 if you don't have dimension 4)Regards,Alain Krikilion
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!0 -
[Topic moved from Navision forum to SQL Performance forum]Regards,Alain Krikilion
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!0 -
Try to have a look at the code executed. NAV Native is still way quicker when it comes to transactions.
Have you tought of beaking into smaller transactions instead of one huge?
Be carefull with the sifts since you don;t want to kill your reporting performance by waiting for matrixforms to populate.
You might also want to consider moving to SSAS for your reporting needs.0
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
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions