Using RG Source Control when deploying multiple copies with slight differences (IDENTITY)
marclallen
Posts: 53 Bronze 3
So, I have a database schema. The code (procs and functions) are all identical. No problem there.
The tables all have identical columns and indexes. But, they have different identity column initial defaults.
Example... I have the following:
CREATE TABLE XXX
(
INT ID PRIMARY KEY CLUSTERED IDENTITY(10000, 1)
...
)
But, when I deploy the next 10 copies of the database, I need different initial IDENTITY values.
Is this something I can handle or work with using Red Gate Source Control? Or with another tool? Or does it require a base deploy and then a custom script to update those values?
(Yes... I know there are better ways than the changing IDENTITY column, but I'm stuck with it at the moment)
Thanks,
Marc
The tables all have identical columns and indexes. But, they have different identity column initial defaults.
Example... I have the following:
CREATE TABLE XXX
(
INT ID PRIMARY KEY CLUSTERED IDENTITY(10000, 1)
...
)
But, when I deploy the next 10 copies of the database, I need different initial IDENTITY values.
Is this something I can handle or work with using Red Gate Source Control? Or with another tool? Or does it require a base deploy and then a custom script to update those values?
(Yes... I know there are better ways than the changing IDENTITY column, but I'm stuck with it at the moment)
Thanks,
Marc
Tagged:
Answers
I'm afraid it's not something our tool can do at the moment. Can you leave your suggestion on our user voice forum?
Thanks!
Tianjiao Li | Redgate Software
Have you visited our Help Center?