That is the situation:

If you have one database with views and those views have references to other database, synchronization fail.

Example:

Origin database name: A
Destination database name B.

One view with something like:

select name from dbo.C.items.

C is other database.
Luis Martin
0

Comments

3 comments

  • Michelle T
    I've been attempting to reproduce this problem, but I'm not exactly sure what you mean by the syntax 'dbo.C.items' - if I attempt to use that syntax exactly in my view (with a different database name instead of C) SQL Server claims it can't find the object. If I use the syntax C..items then SQL Compare synchronizes the view correctly.

    If you could send me the actual view that's failing to synchronize (or preferably the schema for the whole database which it is in, as it might be something else in the database making the view fail to synchronize) to michelle.taylor@red-gate.com that would be very helpful.
    Michelle T
    0
  • Luis Martin
    Ok. I'll send all information by email.
    Luis Martin
    0
  • rdobrich
    Hi,
    Did you mean
    select name from dbo.C.items. (database.schema.object)?

    I have a lot view depending on other database (even on linked server) and everything works fine (if view are fine).

    Often, I have two problem (not with SQL compare, but with creating view).

    One is that underlining object is changed, and the other is that other database is not online (or onother server).

    The best way to check that is to copy script in query window and try to run.

    radovan
    rdobrich
    0

Add comment

Please sign in to leave a comment.