"Name this schema" field to allow the same schema name?
Perhaps I'm not using this correctly but I need to update multiple dbs to a certain schema. Ideally I'd use the same name in the field "Name this schema" when I'm reviewing the change so I can track that the dbs are indeed at the same schema version. Or perhaps there's another way to do this?
Anonymous
shared this idea
Jonathan Hickford
responded
The dashboard spots when two databases have the same schema. If you name it on one database then the dashboard should automatically give the name to your second database. If it’s not doing so then you may have uncovered a bug in the tool – please could you email dlmdashboardsupport@red-gate.com and we can work out what’s happening?The dashboard spots when two databases have the same schema. If you name it on one database
-
Ji
commented
My experience has been that DLM only "spots" that the schema is the same when the database names are identical. Thus they must be on different instances. This is despite the Redgate demo assertions that the matching databases may have different names on the same instance.
-
Anonymous
commented
We are trialling this software, I have 3 Database in pipeline SOMEDB_DEV, SOMEDB_TEST, SOMEDB_PROD.
I have added a new Stored Procedure to DEV and acknowledged the change and called the schema "SOMEDB V2.16.5.1" now when I apply the new new Stored Procedure to TEST and acknowledged the change and calling the schema "SOMEDB V2.16.5.1" I get "There's already a schema with this name." I would logically expect to mark the TEST instance as now using the same scheme and DEV. Is this a bug or design feature I'm missing. I need the functional I described.
-
Kad
commented
I often encounter this exact same issue. I match databases using SQL compare without a single difference, but DLM dashboard still tells me they can't be named the same. Sometime it works and it's automatically recognized... If I were to guess, it's like it's not comparing the schema, but the latest changes batch. If the batch changes to the schema is different, but have the same schema as a end result, it won't recognized that it's the same schema. (from at least 50 observations)
-
Anonymous
commented
Ok. That may be part of the issue. I ran a patch but our dbs were a bit "dirty". They might not have been at the exact same schema.
-
The dashboard spots when two databases have the same schema. If you name it on one database then the dashboard should automatically give the name to your second database. If it's not doing so then you may have uncovered a bug in the tool - please could you email dlmdashboardsupport@red-gate.com and we can work out what's happening?
-
Anonymous
commented
As an example, I was attempting to set the field to "Schema Version 42" across multiple dbs I had upgraded to that version and wasn't allowed to do it. So I had to set e.g. the second db I upgraded to "Schema Version 42 - DB 2"