Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K 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
- 298 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Change primary key on Object table
damir
Member Posts: 28
I have made some analysis on production SQL Server database and found that most used queries are ones involving Object table.
Since primary key (Type,Company Name,ID) on this table has low selectivity, I was wondering if changing it to "ID,Type, Company Name" will bring performance improvement.
I have tried this on my local server. It is working but I am not sure if performance is improved.
What do you think of this idea?
Since primary key (Type,Company Name,ID) on this table has low selectivity, I was wondering if changing it to "ID,Type, Company Name" will bring performance improvement.
I have tried this on my local server. It is working but I am not sure if performance is improved.
What do you think of this idea?
0
Comments
No just kidding
You're right it isn't very selective, but I wouldn't touch the design of a system table. What would probably help is increase the object cache on the client session, that way objects are kept in memory.
RIS Plus, LLC