Comments
Sort by recent activity
Hi Brian,
thanks ! Works perfectly now. / comments
Hi Brian,
thanks ! Works perfectly now.
I just updated to 3.4.0.8 and still have the same issue.
Hans / comments
I just updated to 3.4.0.8 and still have the same issue.
Hans
Apparently this is a frequently occurring issue :
the name of the view was adapated with Enterprise Manager in the DDL. As a result the name of the view in the DDL is different from the one in sysobjects.
The top part of the window uses sysobjects, while the scripts come from the DDL.
I've suggested that future versions of SQL Compare detect such inconsistencies and warn the user and it already seems to be on their to-do list.
Thanks to Brian for investigating this together with us.
Hans / comments
Apparently this is a frequently occurring issue :
the name of the view was adapated with Enterprise Manager in the DDL. As a result the name of the view in the DDL is different from the one in syso...
Hello Brian,
when I ran the compare I assumed the SQL Compare did indeed find the three objects on server A and not on B.
When I ran the query on sysobjects however, I found out that they exist on B (as type V) and not on A. Nevertheless, SQL Compare indicates the opposite (blue arrow pointing from A to [image] and proposes the wrong script (creating objects on B and deleting them from A).
I can send you screenshots and scripts if you like. Company policy does not allow me to put them on a public forum.
thanks
Hans / comments
Hello Brian,
when I ran the compare I assumed the SQL Compare did indeed find the three objects on server A and not on B.
When I ran the query on sysobjects however, I found out that they exist on ...
Hello Brian,
no, the databases are not case-sensitive.
Hans / comments
Hello Brian,
no, the databases are not case-sensitive.
Hans