SQL Compare did not identify a collation difference between source and target databases

SteveNOVSteveNOV Posts: 2
in SQL Compare
I was expecting 3 'Alter Database' statements to update the Collation property of the target database. Will handle manually for now, but just curious if I missed an options or configuration setting.

ALTER DATABASE dbname SET SINGLE_USER WITH ROLLBACK IMMEDIATE;
ALTER DATABASE dbname COLLATE new-collation;
ALTER DATABASE dbname SET MULTI_USER WITH ROLLBACK IMMEDIATE;
Tagged:
· Share on Twitter

Comments

  • SteveNOVSteveNOV Posts: 2
    Additional note: I'm using Trial version 12.2.1.4077 Standard
    · Share on Twitter
  • [Deleted User][Deleted User] Posts: 0 Silver 1
    Hi SteveNOV,

    I've created a ticket with our support team who will get back to you after investigating in more detail. Thanks for the additional information.
    · Share on Twitter
  • Andrew PAndrew P Posts: 194 Silver 3
    Hey SteveNOV,

    Thanks for contacting us!
    We don't currently deploy server/database properties (like the collation) along with the database objects - however, the tool OmniCompare can do that comparison and deployment for a variety of different Server and Database level properties - http://aireforge.com/

    Also, I recommend you post this idea to our UserVoice forum available here

    Do let me know if you have any questions or issues with that!

    Warmly,
    Andrew Pierce
    Technical Sales Engineer
    Redgate Software
    · Share on Twitter
Sign In or Register to comment.