Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Connection Strings
-
We currently use "cliconfg.exe" to maintain our SQL server aliases on each environment.
Thus our connection string can be uniform across environments, e.g. server=TESTDBSERVER;database=Test;uid=sa;pwd=!@#$%A1
When setting up connection strings with BuildMaster though, the connection string is tightly coupled with an environment. Thus I am forced to create a provider for every environment.
Is there a way to decouple this?
P.S. We are only evaluating BuildMaster currently, but as a POC we want to proof we wouldn't need an agent on all database boxes, but can leverage SQL Server Client Network Utility.
-
A similar problem exists with deployables.
Only one deployable can be associated with a connection string.Would be nice if I can associate many deployables with the same connection string and also many environments with the same connection string.
-
The Database Connections module is designed to segregate connection strings in this exact manner; this way, only certain privileged users can use the database connection their privileges allow.
In this case, it might make sense to build a custom Database Provider that's based off of the SQL Server one. This is pretty easy, and several users have done this.
Please contact support, and we will send the source code for this.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login