Clustered Problem

Mally
Member Posts: 128
Dear Concern
I have 2 DB's both in SQL both DB's having table "Payment Terms"(ID 3).In 1 DB the property "Clustered" of key in table 3 is yes and another DB the property "Clustered" of key in table 3 is No.
Can anybody tell me whats the difference between these?Any performance issue is related to this property?
I have 2 DB's both in SQL both DB's having table "Payment Terms"(ID 3).In 1 DB the property "Clustered" of key in table 3 is yes and another DB the property "Clustered" of key in table 3 is No.
Can anybody tell me whats the difference between these?Any performance issue is related to this property?
0
Comments
-
It depends on history of the objects. This property was introduced in one servicepack for NAV 4.00 (I do not know now if it was SP1, SP2 or SP3). If the objects are older, they do not have this property set. If they are newer, they have this property correctly set. If the property is not set in the object, but you are using NAV 4.00SP3, the first key will be created as clustered on SQL. (but there are exceptions and sometime there is no clustered index on the SQL=> very bad performance of whole system).0
-
The Clustered property comes with Navision 4.0 SP1.
If the table is very large and there are many datas in it, and there is no CI, u become a very bad performance as kine said. the reason is, the SQL Server stored the datas not in a sorted structure, it stored it like a heap.Do you make it right, it works too!0 -
Payment terms is a very small table, so it should not be too critical. Worry more about hot tables.David Singleton0
-
0
-
Dear Concern
Anybody please tell me Hot Tables includes whic tables? Please name them?This will help me in solving my problem.0 -
Mally wrote:Dear Concern
Anybody please tell me Hot Tables includes whic tables? Please name them?This will help me in solving my problem.
This list is impossible to make, by definition, every implementation will be different, there are a hand full of "typical" hot tables, but there is no general answer to this question.
Anyone capable of tuning a SQL database will be able to look at your datbase and give you this answer. But if you get any hard answer to this question, then that answer is wrong. Possibly the only table that could always be considered hot is the G/L Entries.David Singleton0
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