Deprecate Linked Servers - by Louis Nguyen

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 780686 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 3/5/2013 7:43:04 AM
Access Restriction Public


In my opinion, Microsoft still appears to be saying that Linked Servers are a viable and recommended option to integrate one SQL instance to another.  In practice, Linked Servers tend to introduce system failures and tight coupling of systems.  e.g. If one SQL instance goes down, the other will rollback transactions.  I don't think most applications are prepared to handle this problem.  MSDTC also introduces another failure point.  Linked Servers also tend to have performance problems, due to inexperienced developers issuing JOINs between two instance.  That is SQL Server often does not create efficient query plans for a query like: select ... from myServerA.myDb.dbo.myTable JOIN myServerB.myOtherDb.dbo.myOther Table etc.   As these are two different SQL instances.  In short, Linked Servers create a low performing, tightly coupled integration with more failure points: network, DTC, and the other SQL instance.

Linked servers: permissions and distributed query performance
Sign in to post a comment.
Posted by jbrauer1 on 6/26/2013 at 10:01 PM
Inexperienced developers using Linked Servers inappropriately is a training issue, not a product issue - this is no reason to remove a feature that other professionals are using appropriately and find invaluable.
Posted by Microsoft on 4/22/2013 at 12:10 PM
After carefully evaluating all of the suggestion items in our pipeline, we are closing items that we will not implement in the near future due to current higher priority items. We will re-evaluate the closed suggestions again in the future based on the product roadmap.

Thanks again for providing the product suggestion and continued support for our product.

Jos de Bruijn