<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Communicate Through Technology &#187; Databases</title>
	<atom:link href="http://www.marbleblue.co.uk/category/databases/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.marbleblue.co.uk</link>
	<description>Web Development, Database Development, Sharepoint Development, Creating websites and we applications using the latest and greatest technologies, Hertfordshire, London, England, UK, Developers and Programmers.</description>
	<lastBuildDate>Sun, 28 Aug 2011 21:20:14 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Linked Server Performance Problem and Collation</title>
		<link>http://www.marbleblue.co.uk/linked-server-performance-problem/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=linked-server-performance-problem</link>
		<comments>http://www.marbleblue.co.uk/linked-server-performance-problem/#comments</comments>
		<pubDate>Mon, 04 Aug 2008 22:01:32 +0000</pubDate>
		<dc:creator>Kushel</dc:creator>
				<category><![CDATA[Databases]]></category>
		<category><![CDATA[Latest]]></category>
		<category><![CDATA[Collation]]></category>
		<category><![CDATA[Collation Name]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[Linked Server]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[performance issues]]></category>
		<category><![CDATA[Remote Collation]]></category>
		<category><![CDATA[server]]></category>
		<category><![CDATA[server objects]]></category>
		<category><![CDATA[server operation]]></category>
		<category><![CDATA[SQL]]></category>
		<category><![CDATA[SQL Server]]></category>
		<category><![CDATA[SQL Server 2005]]></category>
		<category><![CDATA[Sybase]]></category>
		<category><![CDATA[sybase asa]]></category>

		<guid isPermaLink="false">http://www.marbleblue.co.uk/blog/?p=4</guid>
		<description><![CDATA[A potential solution to database performance issues when using linked servers could be the collation settings. 

Click on the title to read more...


No related posts.]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float:right; margin-left: 10px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.marbleblue.co.uk%2Flinked-server-performance-problem%2F"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.marbleblue.co.uk%2Flinked-server-performance-problem%2F" height="61" width="51" /></a></div><p>When using linked server&#8217;s within SQL Server (in our case, 2005), a very important topic to consider is Collation. </p>
<p>I have a SQL Server 2005 database linked to a Sybase ASA database (remote) via an SQL Server Linked Server definition under Server Objects.<br />
<span id="more-4"></span><br />
When setting this up, I set remote collation to true, but I didn&#8217;t specify the collation name (incidentally the collation was the same for both databases). I then started to have some major performance issues when using SQL Server to retrieve data from Sybase. </p>
<p>It turns out that from my understanding, by not setting the collation name, the linked server operation was pulling back a larger set of rows (which could be whole tables), storing them in temporary tables BEFORE sorting them. </p>
<p>By specifically naming the collation, the linked server operation could interrogate the remote table information directly!</p>


<p>No related posts.</p>]]></content:encoded>
			<wfw:commentRss>http://www.marbleblue.co.uk/linked-server-performance-problem/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

