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 |
|
Rob Kramar
Starting Member
1 Post |
 Posted - 2009-07-29 : 14:24:39
|
| I have a need to join tables managed by 2 different SQL Server instances on 2 different servers. One is SQL 2005 and one is SQL 2000.I understand that executing the sp_addlinkedserver stored procedure must be run to facilitate that.Question:Aside from the obvious benefit, is there any downside to creating a Linked Server?Question:If I ever wanted to "undo" this Linked Server creation, how is that accomplished? I don't see a "sp_droplinkedserver" or "sp_deletelinkedserver" in the list of System Stored Procedures that are visible in SQL Server Management Studio.... |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2009-07-29 : 14:58:24
|
| Linked servers can be slow. You'll want to define the security on the linked server so that you don't give access to the remote system to users who shouldn't have access. I always use the "use current security context" option due to this.You would use sp_dropserver to remove the linked server. It can also be done via the GUI in Management Studio.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog"Let's begin with the premise that everything you've done up until this point is wrong." |
 |
|
|
|
|
|
sp_addlinkedserver