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
Clustering in SQL
tapas6324
Member Posts: 35
The Primary Key of Value Entry Table is Clustured Index in SQL Server 2000 & we are going to change the key property to Non-Clustered in SQL.
So is there any bad impact from the Navision(Version 3.7) point of view????
Looking forward for your suggesion & thank you in advance.
Regards,
Paul
So is there any bad impact from the Navision(Version 3.7) point of view????
Looking forward for your suggesion & thank you in advance.
Regards,
Paul
Tapas Paul,
Dubai, UAE.
Dubai, UAE.
0
Comments
Which client version are you using?
Have you tested this?
The clustered index on entry no. is to make the posting process go fast. The speed of posting processes determines the usability of your system.
If you have a reporting issue on a large database, I would recommend seting up a separate reporting database.
How large is your database? How many end users do you have?
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!