Redgate source control when code refers to other Dbs on the same server?
up vote
0
down vote
favorite
Ive looked at Redgate source control before, but have since been using Visual Studio SQL projects and either SVN or Git as a backing SCM. Lately, I've ran into an issue with the compare tool (part of SSDT in Visual Studio), which complicates things when a database object refers to another database on the same server. The approach usually taken is to create DACPAC files for these referenced databases, then create Db references using these DACPAC files. Along with these references are SQLCMD variables which you can then replace your the corresponding values in your code. These SQLCMD variables get used to replace their values with the actual values at build/publish time.
However, currently there seems to be a bug with SSDT and Schema compare that does not allow the compare to work correctly. When doing a project-to-Db schema compare, the area in a procedure for example which uses the SQLCMD variable is seen as "different".
I'm taking a new look at the Redgate Source control. Will it work under the case where for example, a procedure has references to another Db on the same instance?
Just realized I already have a license for it, so will be trying it out.
redgate
asked Nov 9 at 17:23
bitshift
92021027
add a comment |
up vote
0
down vote
favorite
Ive looked at Redgate source control before, but have since been using Visual Studio SQL projects and either SVN or Git as a backing SCM. Lately, I've ran into an issue with the compare tool (part of SSDT in Visual Studio), which complicates things when a database object refers to another database on the same server. The approach usually taken is to create DACPAC files for these referenced databases, then create Db references using these DACPAC files. Along with these references are SQLCMD variables which you can then replace your the corresponding values in your code. These SQLCMD variables get used to replace their values with the actual values at build/publish time.
However, currently there seems to be a bug with SSDT and Schema compare that does not allow the compare to work correctly. When doing a project-to-Db schema compare, the area in a procedure for example which uses the SQLCMD variable is seen as "different".
I'm taking a new look at the Redgate Source control. Will it work under the case where for example, a procedure has references to another Db on the same instance?
Just realized I already have a license for it, so will be trying it out.
redgate
asked Nov 9 at 17:23
bitshift
92021027
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Ive looked at Redgate source control before, but have since been using Visual Studio SQL projects and either SVN or Git as a backing SCM. Lately, I've ran into an issue with the compare tool (part of SSDT in Visual Studio), which complicates things when a database object refers to another database on the same server. The approach usually taken is to create DACPAC files for these referenced databases, then create Db references using these DACPAC files. Along with these references are SQLCMD variables which you can then replace your the corresponding values in your code. These SQLCMD variables get used to replace their values with the actual values at build/publish time.
However, currently there seems to be a bug with SSDT and Schema compare that does not allow the compare to work correctly. When doing a project-to-Db schema compare, the area in a procedure for example which uses the SQLCMD variable is seen as "different".
I'm taking a new look at the Redgate Source control. Will it work under the case where for example, a procedure has references to another Db on the same instance?
Just realized I already have a license for it, so will be trying it out.
redgate
asked Nov 9 at 17:23
bitshift
92021027
Ive looked at Redgate source control before, but have since been using Visual Studio SQL projects and either SVN or Git as a backing SCM. Lately, I've ran into an issue with the compare tool (part of SSDT in Visual Studio), which complicates things when a database object refers to another database on the same server. The approach usually taken is to create DACPAC files for these referenced databases, then create Db references using these DACPAC files. Along with these references are SQLCMD variables which you can then replace your the corresponding values in your code. These SQLCMD variables get used to replace their values with the actual values at build/publish time.
However, currently there seems to be a bug with SSDT and Schema compare that does not allow the compare to work correctly. When doing a project-to-Db schema compare, the area in a procedure for example which uses the SQLCMD variable is seen as "different".
I'm taking a new look at the Redgate Source control. Will it work under the case where for example, a procedure has references to another Db on the same instance?
Just realized I already have a license for it, so will be trying it out.
redgate
redgate
asked Nov 9 at 17:23
bitshift
92021027
asked Nov 9 at 17:23
bitshift
92021027
edited Nov 9 at 18:25
asked Nov 9 at 17:23
bitshift
92021027
asked Nov 9 at 17:23
bitshift
92021027
asked Nov 9 at 17:23
bitshift
92021027
92021027
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53230559%2fredgate-source-control-when-code-refers-to-other-dbs-on-the-same-server%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
