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 |
murrayb3024
Yak Posting Veteran
79 Posts |
Posted - 2013-12-26 : 14:52:39
|
I moved and now work remotely from home. I have a Cisco device I connect through to our network. Since I do this I can't expand any of the linked servers we have on our instances. I have worked with our Network people and we can't seem to find anything on that end that is issue. Is there some setting in SQL server that could be causing the issue? If I remote into another machine I can see them that way, just was hoping to not have to remote into machines just to look up stuff located in those linked servers. Thoughts? |
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2013-12-26 : 15:15:18
|
You'll need to add SQL aliases to your home system. This can be done in SQL Server Configuration Manager or in regedit. This is done on your system and not done on the database server. I almost always use regedit:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectToString value: LinkedServerNameData value: DBMSSOCN,DbServerName,PortNumberChange DbServerName to the server that is being linked to, typically LinkedServerName and DbServerName are identical.Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
|
|
murrayb3024
Yak Posting Veteran
79 Posts |
Posted - 2013-12-26 : 15:34:59
|
I don't have that key in there, and I checked my desktop at work that I can do it from and that key isn't on there either. Also, I just was able to work with those linked servers in SSMS 2008, just not 2005. Any other ideas?quote: Originally posted by tkizer You'll need to add SQL aliases to your home system. This can be done in SQL Server Configuration Manager or in regedit. This is done on your system and not done on the database server. I almost always use regedit:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectToString value: LinkedServerNameData value: DBMSSOCN,DbServerName,PortNumberChange DbServerName to the server that is being linked to, typically LinkedServerName and DbServerName are identical.Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2013-12-26 : 16:08:06
|
Yes it won't be there. You have to create the ConnectTo key. You don't need it at work because your work desktop is able to figure out the port due to being able to reach the SQL browser. Your home desktop isn't able to do that. You can either troubleshoot the SQL browser issue (likely a firewall problem) or simply add the SQL aliases. Adding a SQL alias is the easiest option.Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
|
|
|
|
|