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
- 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
- 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
Options
Sift index and Sql index
Balello
Member Posts: 61
I know that it's possible not to mantain SIFT indexing on SQL or not to mantain a sql index at all.
The question is: is it possible (and does make sense) to mantain sift index and not sql index. For example, consider Item Ledger Entry. I'm interested to mantain the Entry Type, Item No. sum, but not the corresponding key on sql, that's not "selective" on the first field.
To better explain, I think that a good key strategy is to mantain SIFT sums on "not selective" Navision indexes (but not create the SQL index) and mantain SQL indexes only on "selective" indexes (and not SIFT index on them, because of the small quantity of records to sum).
Does the idea make sense?
Thanks in advance.
The question is: is it possible (and does make sense) to mantain sift index and not sql index. For example, consider Item Ledger Entry. I'm interested to mantain the Entry Type, Item No. sum, but not the corresponding key on sql, that's not "selective" on the first field.
To better explain, I think that a good key strategy is to mantain SIFT sums on "not selective" Navision indexes (but not create the SQL index) and mantain SQL indexes only on "selective" indexes (and not SIFT index on them, because of the small quantity of records to sum).
Does the idea make sense?
Thanks in advance.
I don't envy anybody who caught up his aim. I travel gladly.
0
Comments
Try to figure out what the different key properties mean. Open any table in design mode, open the keys form, and make sure that you make all columns visible. Then, for each column, read what F1 help says.
Open the SQL Server Management Studio (or Enterprise Manager for SQL Server 2000), browse to the table you are looking for, and see if you can figure out the link between NAV keys and SQL Server indexes. See what happens when you disable MaintainSQLIndex (don't forget the refresh SQL Server).
As far as SIFT goes, when you enable MaintainSIFTIndex, it creates a separate table for the sumindexfields on SQL Server. See if you can figure out how that link works. Hint: <company name>$<table number>$<SIFT index number>
RIS Plus, LLC
My question focus was on the "completely indipendent" use of the "mantain (SIFT or SQL) index" flag on key properties. And as you answer to me, not only that's possible but it's a good strategy too.
To the next time,
Enrico.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!