"Table already exists" during migration to SQL Server

Nortepe85
Member Posts: 2
Trying to convert my NAV4.0-database to SQL Server. Imported "migration.fob", and ran codeunits 104010 and 104015 and fixed the incorrect dates.
After that I've made an backup of this native database, created an new empty SQL-database en tried to import the backup. After a while, Navision reports that an table already exists.
I've investigated this, and it seems I've many double fields like "Amsterdam" and "AMSTERDAM". Or "1234aa" and "1234AA". SQL Server doesn't like this. Is there a way to fix these issues in the native database?
After that I've made an backup of this native database, created an new empty SQL-database en tried to import the backup. After a while, Navision reports that an table already exists.
I've investigated this, and it seems I've many double fields like "Amsterdam" and "AMSTERDAM". Or "1234aa" and "1234AA". SQL Server doesn't like this. Is there a way to fix these issues in the native database?
0
Answers
-
Got it solved by creating a new database with the NAV-client. On the "Collation-tab" checked "Case-sensitive".0
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