Search

Deprecate Linked Servers by Louis Nguyen

Active

1
0
Sign in
to vote
Type: Suggestion
ID: 780686
Opened: 3/5/2013 7:43:04 AM
Access Restriction: Public
0
Workaround(s)

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
http://sqlblog.com/blogs/linchi_shea/archive/2010/11/22/linked-servers-permissions-and-distributed-query-performance.aspx
Details (expand)

Product Language

English

Category

SQL Engine

Proposed Solution


I would recommend Microsoft update its documentation to stop "advocating" Linked Servers as a first choice mechanism in systems integration.    

Primary Benefit

Improved Performance

Other Benefits


More robust messaging architecture.

Virtualization

 
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 4/22/2013 at 12:10 PM
Hello,
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
Sign in to post a workaround.