CREATE ASSEMBLY are always different after syncronization

edited September 22, 2008 11:26AM in SQL Compare Previous Versions
after comparing two objects of CREATE ASSEMBLY type, SQL Compare still shows differences in FROM clause .

Why does it happen?

The version is 6.2.0.271
Junior Mayhe
Infonapsys - Real information
www.infonapsys.com

Comments

  • Is SQL Compare actually showing the objects as different (i.e. you could select and synchronize them a second time) or are these differences shown in the SQL Differences Panel only?
    Software Developer
    Redgate Software
  • When you install a CLR assembly in your database for the first time, and synchronize it with another database, it showed me that CLR Assemblies were different in the SQL Differences Panel, but without the orange notation on the bottom left corner.

    Nowadays it seems to be ok; the assemblies are equal when I synchronize for the second time and on.

    It was not posible to synchronize it for the first time, but when you run the script below on the target database, you're able to synchronize the databases:

    alter database YOUR_DATABASE_NAME
    set trustworthy on

    As you know, the assemblies are in a notation that is not user friendly:

    --Assembly causaciones, version=0.0.0.0, culture=neutral, publickeytoken=null, processorarchitecture=msil
    CREATE ASSEMBLY [YOUR_ASSEMBLY]
    AUTHORIZATION [dbo]
    FROM 0x4d5a90000300000004000000ffff0000b800000000000000400000000
    000000000000000000000000000000000000000000000000000000000
    000000800000000e1fba0e00b409cd21b8014ccd21546869732070726f6
    772616d2063616e6e6f742062652072756e20696e20444f53206d6f6465
    2e0d0d0a2400000000000000....
    AS 'Properties\AssemblyInfo.cs'
    GO

    In the first time, SQL Differences Panel was showing differences in the FROM Clause of the assembly, but there were no orange indication.
    Junior Mayhe
    Infonapsys - Real information
    www.infonapsys.com
Sign In or Register to comment.