Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
fossm256
Starting Member
3 Posts |
 Posted - 2015-04-28 : 23:04:35
|
| I need to setup an Alias for a Name Instance on SQL server 2012 sp2 CU2. I tried to set it up with SQL System configurator for both 32 bit and 64bit native client alias.on the server where the name instance lives. For both Named Pipes and TCP/IPI go try to connect to it from another SQL server 2012 managementstudios. I get the error for named pipes (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)I know allow remote connection is set to 1. I am running each instance using a different port. SQL Server Browser is running.I went through all the requirements from this web pagehttps://technet.microsoft.com/en-us/library/ms190445(v=sql.120).aspxWhat am I missing. do I have to go to every machine that uses this named instance and setup the alias for the name instance. I am checking it by trying to connect to using SSMS on another serverusing the alias.I have setup link servers before with no problems, but I can not get it to work for named instances alias. I am trying to consolidate 3 servers to 1 server with a named instance for each of the servers. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2015-04-29 : 12:06:30
|
| The alias goes on the machine where you are getting the error, not on the server itself unless the alias is needed there for other reasons (there are good reasons).Or fix why the browser service can't be reached.Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
 |
|
|
fossm256
Starting Member
3 Posts |
Posted - 2015-04-29 : 14:20:19
|
| So you are saying every computer that accessed server a.instanceI need to add an alias for the new server.b |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2015-04-29 : 14:25:40
|
| Every computer that has an issue, yes. You can easily mass-deploy it through a Windows login script or whatever they are called. Chat with your server admin.Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
|
|
|
fossm256
Starting Member
3 Posts |
Posted - 2015-05-06 : 10:49:02
|
| I am going to try another approach.I am going to assign an IP address to each instance using SQL Server configuration manager.Then in DNS, assign an alias for each IP address. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2015-05-06 : 15:36:07
|
| But what matters is the port that the SQL instance is listening on. DNS can't help with that. You need an alias on each client machine that has this issue or figure out why the clients can't communicate with the SQL Browser service on the database server.Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
|
|
|
|
|
|
SQL Server Alias for Named Instances