SQL Transformations
furier
Posts: 3
Hi
I was wondering if DLM Automation support SQL Transformations?
I have an issue were we use synonymes from one database to talk to a second database and they both have evironment specific names with endings like *_Dev or *_Prod
The TeamCity Build Step: Redgate DLM Automation Build, failes with errors saying the X database does not exist when doing the validation step.
I could just fix the failing build step by creating X databases on that server, however when I want to use OctopusDeploy to deploy to different environments I need to make sure that the synonymes are correct for each environment.
if DatabaseName = AccessIT_B1_Dev
I was wondering if DLM Automation support SQL Transformations?
I have an issue were we use synonymes from one database to talk to a second database and they both have evironment specific names with endings like *_Dev or *_Prod
The TeamCity Build Step: Redgate DLM Automation Build, failes with errors saying the X database does not exist when doing the validation step.
I could just fix the failing build step by creating X databases on that server, however when I want to use OctopusDeploy to deploy to different environments I need to make sure that the synonymes are correct for each environment.
if DatabaseName = AccessIT_B1_Dev
CREATE SYNONYM [bhold].[AuditorRuns] FOR [%DatabaseName%].[dbo].[AuditorRuns]should output
CREATE SYNONYM [bhold].[AuditorRuns] FOR [AccessIT_B1_Dev].[dbo].[AuditorRuns]
Comments
If this is something that you would like to see implemented, then I suggest that you post the suggestion on our Uservoice site - there you can make suggestions and vote on suggestions that other users have made.
Redgate Software