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

There is already a schema with this name

Am I limited to having a version of a schema across all databases on one instance?

I have two databases being monitored on one instance, but when I tend to acknowledge changes and set the schema to version 1.3 for database 2, I get the error that this schema exists, even though it only exists for database 1.
way0utwest
0

Comments

3 comments

Sort by
  • Sergio R
    Hi,

    I am afraid that this is by design: schema name should be unique within a pipeline and since it is possible to move schemas between pipelines they need to be unique globally.

    I suggest you use a unique prefix to each database, for example: DB1 - version 1.3 and DB 2 - version 1.3

    Thank you,
    Sergio R
    0
  • jnguyen714
    Hi,

    Can the "name this schema" be disable on the review page?

    Thanks,
    Johnny
    jnguyen714
    0
  • carthorn
    So, what if a schema in two difference databases matches 100% in Compare 11, shouldn't DLM also see that those schema's match?
    carthorn
    0

Add comment

Please sign in to leave a comment.