I'm working with a team of developers who have SQL instances installed in different places. For the purposes of having one config file for our local machines (instead of having a config file for each machines) we're trying to deal with the SQL installed with instance names, no instance names, etc:
I looked at this guide to setting up alias redirects but when we create the same alias name, say "MyOldServer" I get errors on connecting to an untrusted domain using Windows authentication.
Short of reinstalling SQL to the same place on all these machines? How can we make it so that they're all pointing to the same name (preferably (local) but I don't care either way.
Edit: My connection string (working)
<add name="masterDb" connectionString="integrated security=true;Data Source=(local);Database=masterDb" />
Colleague's connection string (also working on their local machine)
<add name="masterDb" connectionString="integrated security=true;Data Source=(local)\local;Database=masterDb" />
We would like to use one or the other so we have one local config checked into source. I'm okay with changing both our connection strings ... but I'd like us to have the same connection string without installing SQL if possible. We're onloading more developers and having them all reinstall SQL to conform will be cumbersome.
Alias configuration (my machine):
Alias Name: TestAlias Port no: blank Portocol: TCP/IP Server: localhost
If I added TestAlias to my hosts file, and try to connect (using SQL configuration manager) to Server name: testalias, and windows authentication, I get "Login failed. The login is from an untrusted domain and cannot be used with Windows Authentication"