Packages and compresses schema and contents of SQL Server databases
Moderators: JonathanWatts, Chris Auckland, David Atkinson, david connell, Anu Deshpande, Michelle Taylor, james.billings, Marianne
I have a SQL Script that I am attempting to package that is currently 239, 343 lines in length.
The majority of this is reference data so that data script generated by the packager is about 85% of the total length.
My source script contains both English and French text and this includes accented characters such as é.
When I install from my source script to a SQL 2012 instance, the accented characters are preserved but when I package the script into an .exe using Packager the resulting installation has replaced the accented characters with question marks.
Has this behaviour been observed before? Is there anything I can do to prevent this?
- Posts: 1
- Joined: Wed May 01, 2013 9:56 am
- Location: Leicester, UK
This is usually a function of the underlying text encoding (for example ANSI vs Unicode (UTF xx).
*My* way of solving this is, using a free text editor such as Notepad ++, check the encoding of the original text files- test if it works better when they are all UTF or all ANSI.
I hope that helps.
- Posts: 594
- Joined: Thu Mar 12, 2009 4:17 pm
Return to SQL Packager 6
Who is online
Users browsing this forum: No registered users and 0 guests