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

Owner mapping issues

A few odd things happening...

1. Set up compare Server1, database A to Server 1, database B
2. Unmap dbo, set mapping dbo <-> Schema1 (now database A owner list is empty, database B owner list has dbo Unmapped)
3. Compare Now - Realize Synchronization needs to go the other way and the popular Arrow reversal won't be available for another month.
4. Edit Project, click switch.
5. Compare Now - Owner Mappings have been reset instead of switched.
6. Edit Project, click Mapping, Unmap dbo, set mapping Schema1 <-> dbo (now database A owner list has dbo Unmapped, database B owner list is empty)
7. Abort message [Schema1] is trying to map to [dbo], which is unmapped. SQL Compare does not like having dbo Unmapped on the left side, but is OK if dbo is unmapped on the right side. I don't have an extra schema on the right, so I can't map the leftover dbo to anything to proceed with the compare.
8. Manually undo the Schema1 <-> dbo mapping, and map dbo <-> dbo again.
9. Compare Now - Error Message - SQL Compare 8 has encountered a problem and needs to close

Thanks,
Traci
tkdennis
0

Comments

4 comments

Sort by
  • Simon C
    Could you try this on the release candidate? Several bugs relating to mappings have been fixed between the beta and the RC

    Simon C
    Simon C
    0
  • tkdennis
    Using RC1, I was able to get to the compare results, but when I tried to synchronize an object (right-to-left), I got the message "There is an unmapped user or schema. Please check your mappings." So it still doesn't like that I have an uneven number of schemas and leave the dbo schema unmapped on one side.
    tkdennis
    0
  • Simon C
    With the new mappings, you can't leave dbo unmapped on one side. Am I correct in thinking your mappings are like this:
    Source           Target
Schema1 &lt;-&gt; dbo
dbo         &lt;-&gt;

    If so, SQL Compare shouldn't compare the database like this. Internally, SC creates a clone of the source database and manually applies all the mapping renames and refactorings to the clone. Here, Schema1 will be renamed to dbo. The problem is, dbo already exists, and isn't mapped to anything itself. If there is a [Schema1].[table1] and [dbo].[table1] in the source, or even permissions on the Schema1 or dbo schema objects that aren't on the other, we don't know which one to use. So I'm afraid you can't map a schema onto one that already exists; a workaround is to create a Schema2 in the target and map dbo in the source to Schema2 in the target.
    Simon C
    0
  • tkdennis
    It let me do the Compare, but not the synchronize. I may have switched the databases so the unmapped dbo was on the right. The actual case was comparing 2 databases, one had schema "stage" that mapped to the second database schema "dbo". The second database didn't have any extra schemas, so there was nothing to map the first database dbo schema to. I wound up moving all the tables in the first database back to the dbo schema since using different schemas for stage<->dbo was causing other confusion. Now we are just using schemas to keep objects from the same data owners grouped together, and they don't compare to anything else so it's not an issue anymore since dbo is mapped to dbo again.

    Thanks for your help, and I really like the new SQL Compare!
    Traci
    tkdennis
    0

Add comment

Please sign in to leave a comment.