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
SQL Sift Tables
jordi
Member Posts: 2
Hi all,
I am from a NSC in Malaysia. As you have known, Navision is quite new here. So our exposure to SQL here is quite limitted. We need all the help we can. <img border="0" title="" alt="" src="images/smiles/icon_smile.gif" />
I understand that SQL does not handle SIFT tables very well. Below are the drawbacks I have received regarding Navision on a SQL Server.
1. SIFT tables are only updated via the restore operation in the Navision program. How does this affect development in Navision in areas using flowfields and areas not using flowfields?
2. If it is true that SIFT are only updated via the restore operation in Navision program, are there any other ways to update the SIFT table, eg. a general stored procedure?
3. It is STRONGLY not recommended for a Navision SQL Server to have more than 1 company in its database. How true is this?
A million thankx.
Jordi
Technical Specialist
I am from a NSC in Malaysia. As you have known, Navision is quite new here. So our exposure to SQL here is quite limitted. We need all the help we can. <img border="0" title="" alt="" src="images/smiles/icon_smile.gif" />
I understand that SQL does not handle SIFT tables very well. Below are the drawbacks I have received regarding Navision on a SQL Server.
1. SIFT tables are only updated via the restore operation in the Navision program. How does this affect development in Navision in areas using flowfields and areas not using flowfields?
2. If it is true that SIFT are only updated via the restore operation in Navision program, are there any other ways to update the SIFT table, eg. a general stored procedure?
3. It is STRONGLY not recommended for a Navision SQL Server to have more than 1 company in its database. How true is this?
A million thankx.
Jordi
Technical Specialist
0
Comments
I'm afraid I don't understand your questions in full.
The SIFT (Sum Index Flow Technology) tables are separated from the main tables under SQL, but still an integrated part of the database. Updating the values in these tables is done automagically in the background, yet the results are immediately available for display by any flowfield, just like running native Navision.
When you define a flowfield, Navision will create the SIFT table(s) as required. Importing a FOB (compiled (Navision) Financials OBjects) is sufficient to get everything in place, no need for a full restore of the database.
Having more than one company is no problem at all under SQL. We have customers running over ten companies, with a complicated mix of shared and not-shared tables.
John