Red Gate forums :: View topic - SQL Collations with Version 6
Return to www.red-gate.com RSS Feed Available

Search  | Usergroups |  Profile |  Messages |  Log in  Register 
Go to product documentation
SQL Packager 6
SQL Packager 6 forum

SQL Collations with Version 6

Search in SQL Packager 6 forum
Post new topic   Reply to topic
Jump to:  
Author Message
olli_d



Joined: 30 Nov 2007
Posts: 9

PostPosted: Mon Jan 26, 2009 3:00 pm    Post subject: SQL Collations with Version 6 Reply with quote

I'm missing the SQL Collations. Is that really true? What about compatibilty to old database schema?
Or did I miss some options to set the collation?
Back to top
View user's profile Send private message
Michelle Taylor



Joined: 30 Oct 2006
Posts: 529
Location: Red Gate Software

PostPosted: Mon Jan 26, 2009 5:05 pm    Post subject: Reply with quote

Where are you missing the SQL Collations, and what versions of SQL Server are you using in the project? We tried to only provide collations that the target version of SQL Server would accept, but we shouldn't have deleted all the backwards compatibility collations from the list at any point.
Back to top
View user's profile Send private message
olli_d



Joined: 30 Nov 2007
Posts: 9

PostPosted: Mon Jan 26, 2009 5:16 pm    Post subject: SQL Collations on SQL 2005 Reply with quote

All MS SQL Server Versions 2005 below use SQL Collations. I'm using SQL_Latin1_General_CP1_CI_AS.
Please see 'new database' dialog or 'server properties' dialog during install to see these entries. With Packager 5 all was fine.
Chris
Back to top
View user's profile Send private message
olli_d



Joined: 30 Nov 2007
Posts: 9

PostPosted: Wed Jan 28, 2009 4:58 pm    Post subject: Collations are present - until ... AND another Bug Reply with quote

... until I select SQL 2005 compatibility level -> then the disappear from the combobox. <server default> is selected instead.
AND the List does NOT show any SQL-Collations anymore.

BTW: 2nd Bug: Leaving the Compatibilty Level emtpy to keep the SQL-Collation entry (should have been my workaround) will result in an non executable package)!

Haven't got any feedback for 24 hours, redgate Sad. I'm stuck right now.

Chris
Back to top
View user's profile Send private message
olli_d



Joined: 30 Nov 2007
Posts: 9

PostPosted: Thu Jan 29, 2009 7:58 pm    Post subject: ... anybody out there? Reply with quote

Hi Michelle,
any news on this topic? I do need support.
Back to top
View user's profile Send private message
Michelle Taylor



Joined: 30 Oct 2006
Posts: 529
Location: Red Gate Software

PostPosted: Thu Jan 29, 2009 8:10 pm    Post subject: Reply with quote

The compatibility level making the sql collation list not contain SQL collations is a bug Sad. I managed to make a package when I tried to go for one leaving the compatibility level empty with the collation you specified, and haven't been able to make that fail.

If you could give me some more details on exactly what you're doing when the package fails to execute? (i.e. C# or exe, what database version on each side, what things you change on the last screen of the wizard)
Back to top
View user's profile Send private message
olli_d



Joined: 30 Nov 2007
Posts: 9

PostPosted: Thu Jan 29, 2009 8:33 pm    Post subject: Reply with quote

MS Vista SP1 x64 english 4 GB RAM
SQL 2005 Standard SP3 german
Packager:
- pack all tables, all records
- .exe not compressed
- SQL Collation SQL_Latin CP1_CI_AS
- Recovery simple
- Compatibility <server default> !not having touched this combo!
- no changes on file locations
- no change on database size
- no change on database name

- package name with xxx_20090127


I was now also able to create a new package the way you described. The process failed before - probably because I set up the package based on a Packager v5 file.

Do you need any further info?
Back to top
View user's profile Send private message
Michelle Taylor



Joined: 30 Oct 2006
Posts: 529
Location: Red Gate Software

PostPosted: Fri Jan 30, 2009 12:54 pm    Post subject: Reply with quote

Are you now able to use the workaround of not setting the compatibility level (and we'll hopefully fix the bug when we next have a new version of Packager), or is there an immediate problem you still have with the product?

I'll have a go at reproducing the backwards compatibility problem, but it might be easier if you could send me the offending project file (to michelle.taylor@red-gate.com).
Back to top
View user's profile Send private message
olli_d



Joined: 30 Nov 2007
Posts: 9

PostPosted: Thu Oct 29, 2009 2:45 pm    Post subject: It's blocking now Reply with quote

Michelle,
the error in SQL Packager is going to be blocking now because 'Server default' collation is different to our sql-collation.
Some update scripts do not work with these different collations. When you previously asked whether the problem allows a workaround I never expected the error not to be fixed. I definitely need an update now. The error already took us much time to work around, communicate an fix.

Please save our good impression on Red Gate Products and Support.
Chris
Back to top
View user's profile Send private message
olli_d



Joined: 30 Nov 2007
Posts: 9

PostPosted: Mon Nov 09, 2009 7:34 am    Post subject: It's fixed now Reply with quote

Many thanks for your quick and solid fix of the error and the direct contact to you, Chris during fixing the problem.
Packager is doing now what it is supposed to do.
Chris
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic All times are GMT + 1 Hour
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group