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
- 300 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 35 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
Different "encoding" after restoring database
martinhocosta88
Member Posts: 27
Hello,
Lately I have been moving some databases from a local environment to Azure. All the data that contains the symbol "~" got a diferent encoding.
Even though the default collation from both instances are slightly diferent, the database collations (that i think it overwrites the instance default collation) is the same in both sides.
Any clue on what am I missing?
Lately I have been moving some databases from a local environment to Azure. All the data that contains the symbol "~" got a diferent encoding.
Even though the default collation from both instances are slightly diferent, the database collations (that i think it overwrites the instance default collation) is the same in both sides.
Any clue on what am I missing?
0
Best Answer
-
wakestar
Member Posts: 207
I assume your virtual machine has United States in the regional settings. Change that to whatever you usually work with5
Answers
https://sqlazuremw.codeplex.com/
that's what I meant with regional settings