Business Analytics with SQL2005 - Case Sensitive
jigsaw
Member Posts: 7
When the Configurator runs in Nav 4.0 SP3 on SQL Server 2005 the SSIS package fails. The issue appears to related to Case Sensitivity.
In simple terms
- my SQL Server 2005 is set to be Case Sensitive and Accent Sensitive (CS_AS)
- when I run "Start the Configurator" the wizard runs the the "BA for MBS Navision" is being created with the Servers collation CS_AS
- the SSIS package fails when it tries to validate/query the table Information_Schema.Tables as the real name in the database is INFORMATION_SCHEMA.TABLES (Notice difference in case)
(I can tell what the error is by manually running the SSIS script)
I am not in a situation where I can change the servers collation to be case insensitive.
I can't see how I can change the way the package is built as the details appear to be encapsulated in the Configurator.exe file.
In simple terms
- my SQL Server 2005 is set to be Case Sensitive and Accent Sensitive (CS_AS)
- when I run "Start the Configurator" the wizard runs the the "BA for MBS Navision" is being created with the Servers collation CS_AS
- the SSIS package fails when it tries to validate/query the table Information_Schema.Tables as the real name in the database is INFORMATION_SCHEMA.TABLES (Notice difference in case)
(I can tell what the error is by manually running the SSIS script)
I am not in a situation where I can change the servers collation to be case insensitive.
I can't see how I can change the way the package is built as the details appear to be encapsulated in the Configurator.exe file.
0
Comments
-
You cannot change the server collation, but are you able to change the DB collation?0
-
The Collation of the NAV DB does not matter.
The BA for MBS Navision" DB is dropped and re-created each time, and inherits the Servers Collation.0 -
This issue is due to a bug in the BA Configurator. The only quick fix is to re-install the SQL Server2005 as case in-sensitive which is not always an available option.
MS are looking into the issue further.0 -
Hmmm... it seems like the testers in MS are not creative enough to test all possibilities... 8)0
-
Hi,
I'm running NAV 4.0 SP3 SQL2005 and I've got the same error. The SSIS package fails. The message in the event viewer is "Origin: SQLISPackage, ID 12291".
I reinstalled SQL as case insensitive but I've got the same error. Do you think that I have to check other parameters?
Thanks!0 -
To build cubes in Italian release of NAV 4.0/SP3 (Build 23305) SQL 2005 the Windows international options in the control panel must be set to English, otherwise the Configurator fails because of dates format.0
Categories
- All Categories
- 75 General
- 75 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K 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
- 611 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 253 Dynamics CRM
- 103 Dynamics GP
- 6 Dynamics SL
- 1.5K Other
- 991 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 28 Design Patterns (General & Best Practices)
- Architectural Patterns
- 9 Design Patterns
- 4 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1K General Chat
- 1.6K Website
- 77 Testing
- 1.2K Download section
- 23 How Tos section
- 249 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
