Comments
Sort by recent activity
Hi Peter,
The synonyms are pointing to the database correctly.
I've had a look at the build steps but that doesn't have the database name under advanced options.
I select the runner type as 'Redgate DLM Automation Build', and the advanced options are showing 'Additional parameters' and 'Temporary database name'. Also shows 'Execute Steps' but further up underneath 'Step Name'.
One thing I have noticed is that if I follow this blog https://www.red-gate.com/blog/database-lifecycle-management/deploying-cross-database-dependencies and convert the function calls (which are using the synonyms) to stored procedures, the build works.
I have given the TeamCity user the sysadmin role so I can't seem to think it's an issue there.
Your help is much appreciated. / comments
Hi Peter,
The synonyms are pointing to the database correctly.
I've had a look at the build steps but that doesn't have the database name under advanced options.
I select the runner type as 'Redgat...
Hi Peter,
I've gone down the route of this article (http://workingwithdevs.com/cross-database-dependencies-and-automated-builds/) which was a solution which I knew about but wasn't entirely keen on.
I spoke to one of your pre-sales engineers who explained the reasoning behind the decision and it makes sense in what Red Gate was trying to achieve.
So for anyone out there who is using synonym's, ensure which ever environment your database is being built in, also has the databases you're referencing e.g. DB1 has a synonym pointing to DB2, when you use DLM Automation (in my case through TeamCity), ensure that the TeamCity build step is using the same 'Temporary Database Server' details where both databases are residing. They can be empty shells of the databases in question, but that is enough for DLM Automation to reference them and build correctly.
Thank you for your help. / comments
Hi Peter,
I've gone down the route of this article (http://workingwithdevs.com/cross-database-dependencies-and-automated-builds/) which was a solution which I knew about but wasn't entirely keen on...
Hi,
I've had a look around the forum and I found someone else who was having the same issue as I am (https://forums.red-gate.com/viewtopic.php?t=20791).
The problem is that the CI database is sitting on a different server as to the version controlled databases. The reason why it worked locally was the CI (TeamCity) database was on the dev machine which also had the other databases on there so it could reference them with out any issues.
Now the question is, how do I use synonyms in functions and use DLM Automation to build the database? That is without rewriting 100+ stored procedures (along with numerous front end calls) as mentioned here (https://www.red-gate.com/blog/database-lifecycle-management/deploying-cross-database-dependencies). / comments
Hi,
I've had a look around the forum and I found someone else who was having the same issue as I am (https://forums.red-gate.com/viewtopic.php?t=20791).
The problem is that the CI database is sitti...
I've done further testing and it seems to be an issue with using synonym's. The database which built perfectly before, now doesn't build with the same error.
NOTE: Both of the databases build fine on a dev machine but not on a server.
Can someone please get back to me with a solution.
Thank you / comments
I've done further testing and it seems to be an issue with using synonym's. The database which built perfectly before, now doesn't build with the same error.
NOTE: Both of the databases build fine ...