How can we help you today? How can we help you today?

problem with assembly

Hi,
I just run into one problem with assembly and clr function.

This is situation.
In destination server I have old assembly with one function.
In source server I have new assembly with two new functions. The old one referenced with assembly is the same.
When I try to sync, SQL compare generate CREATE assembly, not ALTER assembly, and of cource, faild because can't drop old assembly been referenced in exissting (same) function.

I have to include all dependances functions (check box in script), then sync databases. After that I have manualy set security (which is different from my souce server). Users can't work during that time.

ALTER ASSEMBLY instead DROP and CREATE ASSEMBLY save's me a lot time (and problems)

Radovan
rdobrich
0

Comments

2 comments

Sort by
  • Michelle T
    Do you need to synchronize any permissions in this synchronization that you're performing? If not, then you might want to look at the Ignore Permissions option - if the only problem with synchronizing all the functions is that the permissions are changed to the wrong values, putting on Ignore Permissions would prevent SQL Compare from synchronizing the permissions on the functions.
    Michelle T
    0
  • rdobrich
    The probles is not permission.
    I don't wont to sync them. I set ignore permision and it works fine.

    The problem is that if I change assembly, and create new CLR function, sql compare generate CREATE ASSEMBLY, not ALTER ASSEMBLY.

    That implicate in droping all CLR function existing in that assembly.

    I just wont ALTER ASSEMBLY and create new function (new CLR function witnin assembly)
    rdobrich
    0

Add comment

Please sign in to leave a comment.