There is already a schema with this name

way0utwest · February 5, 2016 5:26PM

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.

Sergio R · February 8, 2016 10:01AM

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,

jnguyen714 · February 24, 2016 6:51PM

Hi,

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

Thanks,
Johnny

carthorn · May 25, 2016 3:10PM

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

There is already a schema with this name

Comments

Product Learning

Community Forums

Events & Friends

Simple Talk