Note that there are some explanatory texts on larger screens.

plurals
  1. POHow can I setup MSSQL2005 to respond to "localhost" and another name at the same time?
    primarykey
    data
    text
    <p>I am working on a code base that has a number of connection strings that access a database server by a specified name.</p> <pre><code>&lt;add name="myConnection" connectionString="Data Source=DevServer;Initial Catalog='devData';Persist Security Info=True;User ID=devUser;Password=devPass;" providerName="System.Data.SqlClient" /&gt; </code></pre> <p>I am in a location that does not have access to the named "DevServer" Data Source.<br> I have a version of the database hosted locally in "localhost".<br> What I would like to do is have my "localhost" database accessible via the Data Source named "DevServer". </p> <p>I don't want to lose the ability to access the server via "localhost" as I have other projects that use this as a Data Source. I <em>could</em> alter the config files, but I would then have to ensure that I don't check them in, as that would break the configuration for others. I still want to receive any updates to the config files, so having local writeable versions is not an option.</p> <p>I have tried using the SQL Server Configuration Manager to create an Alias, but I think that I did something wrong as I am still unable to connect using "DevServer".</p> <p>Should SQL Server Configuration Manager be able to achieve what I am trying?<br> Can anyone suggest a way that I can achieve this?</p> <p>I guess my question is similar to <a href="https://stackoverflow.com/questions/449607/point-to-localhost-sqlexpress-using-only-localhost">this</a> but there has been no accepted answer and it is for SQL Express.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload