<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlblog.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Using linked servers, OPENROWSET and OPENQUERY</title><link>http://sqlblog.com/blogs/buck_woody/archive/2010/03/16/using-linked-servers-openrowset-and-openquery.aspx</link><description>SQL Server has a few mechanisms to reach out to another server (even another server type) and query data from within a Transact-SQL statement. Among them are a set of stored credentials and information (called a Linked Server ), a statement that uses</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>re: Using linked servers, OPENROWSET and OPENQUERY</title><link>http://sqlblog.com/blogs/buck_woody/archive/2010/03/16/using-linked-servers-openrowset-and-openquery.aspx#23453</link><pubDate>Tue, 16 Mar 2010 16:29:30 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:23453</guid><dc:creator>NULLgarity</dc:creator><description>&lt;p&gt;Couldn't agree more. &amp;nbsp;Linked servers should only be for ad-hoc access, not for production-delivered code.&lt;/p&gt;
</description></item><item><title>re: Using linked servers, OPENROWSET and OPENQUERY</title><link>http://sqlblog.com/blogs/buck_woody/archive/2010/03/16/using-linked-servers-openrowset-and-openquery.aspx#23472</link><pubDate>Wed, 17 Mar 2010 03:19:55 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:23472</guid><dc:creator>Linchi Shea</dc:creator><description>&lt;p&gt;&amp;gt; &amp;nbsp;Linked servers should only be for ad-hoc access, not for production-delivered code.&lt;/p&gt;
&lt;p&gt;Are you kidding?&lt;/p&gt;
</description></item><item><title>re: Using linked servers, OPENROWSET and OPENQUERY</title><link>http://sqlblog.com/blogs/buck_woody/archive/2010/03/16/using-linked-servers-openrowset-and-openquery.aspx#23483</link><pubDate>Wed, 17 Mar 2010 14:01:45 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:23483</guid><dc:creator>Adam Machanic</dc:creator><description>&lt;p&gt;Alternate solutions might have more potential to scale, but at what cost to develop and maintain? Linked servers are cheap and easy to implement, and not everyone has the time or resources to invest in complex solutions using Service Broker or middle tier applications. Sometimes--actually, most times--getting -something- up and working today is more important than finding the perfect solution in weeks or months.&lt;/p&gt;
&lt;p&gt;Microsoft should invest more time in making linked servers work better when both ends are SQL Server. Every single customer I visit makes extensive use of linked servers, for better or for worse, and almost never with remote sources other than SQL Server. This is not going to go away any time soon, and use cases are certainly not limited to non-production purposes. Quite the opposite, actually.&lt;/p&gt;
</description></item><item><title>re: Using linked servers, OPENROWSET and OPENQUERY</title><link>http://sqlblog.com/blogs/buck_woody/archive/2010/03/16/using-linked-servers-openrowset-and-openquery.aspx#23495</link><pubDate>Wed, 17 Mar 2010 17:59:52 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:23495</guid><dc:creator>NULLgarity</dc:creator><description>&lt;p&gt;I wasn't kidding. &amp;nbsp;However, re-reading what I wrote and Adam's subsequent comments, I should have phrased it differently and not made such a sweeping generalization.&lt;/p&gt;
&lt;p&gt;I should have said that I &amp;quot;try&amp;quot; to only use linked servers for ad-hoc type access and that I &amp;quot;try&amp;quot; to avoid using them in production code. &amp;nbsp;I also could have said that I am skeptical when I see a linked server-centric architecture by design (versus as a workaround).&lt;/p&gt;
&lt;p&gt;I don't disagree with anything that Adam said. &amp;nbsp;I also have found SSIS and snapshot replication to be cheap alternatives to linked servers in some cases, depending on how the linked servers are being used and the requirements.&lt;/p&gt;
</description></item><item><title>re: Using linked servers, OPENROWSET and OPENQUERY</title><link>http://sqlblog.com/blogs/buck_woody/archive/2010/03/16/using-linked-servers-openrowset-and-openquery.aspx#23523</link><pubDate>Thu, 18 Mar 2010 14:13:10 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:23523</guid><dc:creator>Linchi Shea</dc:creator><description>&lt;p&gt;I don't see why linked servers should only be used for 'ad hoc' accesses. In particular, when it's used as a RPC mechanism, it is fantastically useful in many prod environments. Sure, the implementation can be much improved. But 'trying' to limit it to ad hoc use only serves to limit your ability to access info in a distributed envrionment.&lt;/p&gt;
&lt;p&gt;Note that linked servers are not for moving data. They are configurations for accessing data. There is a big difference between moving data and accessing data.&lt;/p&gt;
</description></item></channel></rss>