<?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>Cypris' lookout &#187; SQL Server</title>
	<atom:link href="http://blog.nkadesign.com/category/programming/database/sql-server/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.nkadesign.com</link>
	<description>Just another programming weblog</description>
	<lastBuildDate>Mon, 12 Jul 2010 09:52:36 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Access: Run-time Error 3155 ODBC insert on a linked table failed</title>
		<link>http://blog.nkadesign.com/2009/access-run-time-error-3155-odbc-insert-on-a-linked-table-failed/</link>
		<comments>http://blog.nkadesign.com/2009/access-run-time-error-3155-odbc-insert-on-a-linked-table-failed/#comments</comments>
		<pubDate>Thu, 11 Jun 2009 08:26:06 +0000</pubDate>
		<dc:creator>Renaud</dc:creator>
				<category><![CDATA[Database]]></category>
		<category><![CDATA[MSAccess]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[SQL Server]]></category>

		<guid isPermaLink="false">http://blog.nkadesign.com/?p=606</guid>
		<description><![CDATA[I have been spending a lot of time trying to find out why some of the code used to insert new records into a linked SQL Server table would systematically fail with an error: Run-time Error '3155' ODBC--insert on a linked table failed It was driving me mad. I could insert a simple record using [...]]]></description>
		<wfw:commentRss>http://blog.nkadesign.com/2009/access-run-time-error-3155-odbc-insert-on-a-linked-table-failed/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Access vs SQL Server: some stats (part 1)</title>
		<link>http://blog.nkadesign.com/2009/access-vs-sql-server-some-stats-part-1/</link>
		<comments>http://blog.nkadesign.com/2009/access-vs-sql-server-some-stats-part-1/#comments</comments>
		<pubDate>Mon, 13 Apr 2009 04:00:53 +0000</pubDate>
		<dc:creator>Renaud</dc:creator>
				<category><![CDATA[Database]]></category>
		<category><![CDATA[MSAccess]]></category>
		<category><![CDATA[SQL Server]]></category>

		<guid isPermaLink="false">http://blog.nkadesign.com/?p=527</guid>
		<description><![CDATA[In the perspective of upsizing my current Access 2007 application, I have been trying to understand a bit more about the possible performance impact of various choices of Primary Keys. My problem is that currently, the Access application uses autoincrement numbers as surrogate Primary Keys (PK). Since I will need to synchronise the data over [...]]]></description>
		<wfw:commentRss>http://blog.nkadesign.com/2009/access-vs-sql-server-some-stats-part-1/feed/</wfw:commentRss>
		<slash:comments>15</slash:comments>
		</item>
		<item>
		<title>Sysadmin: SQL server performance madness</title>
		<link>http://blog.nkadesign.com/2009/sysadmin-sql-server-performance-madness/</link>
		<comments>http://blog.nkadesign.com/2009/sysadmin-sql-server-performance-madness/#comments</comments>
		<pubDate>Sun, 12 Apr 2009 11:25:56 +0000</pubDate>
		<dc:creator>Renaud</dc:creator>
				<category><![CDATA[Database]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[SQL Server]]></category>
		<category><![CDATA[sysadmin]]></category>

		<guid isPermaLink="false">http://blog.nkadesign.com/?p=550</guid>
		<description><![CDATA[I&#8217;ve just lost 2 days going completely bananas over a performance issue that I could not explain. I&#8217;ve got this Dell R300 rack server that runs Windows Server 2008 that I dedicate to running IIS and SQL Server 2008, mostly for development purposes. In my previous blog entry, I was trying some benchmark to compare [...]]]></description>
		<wfw:commentRss>http://blog.nkadesign.com/2009/sysadmin-sql-server-performance-madness/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Access: building &#8216;upsizable&#8217; applications.</title>
		<link>http://blog.nkadesign.com/2009/access-building-upsizable-applications/</link>
		<comments>http://blog.nkadesign.com/2009/access-building-upsizable-applications/#comments</comments>
		<pubDate>Wed, 01 Apr 2009 03:39:45 +0000</pubDate>
		<dc:creator>Renaud</dc:creator>
				<category><![CDATA[Database]]></category>
		<category><![CDATA[MSAccess]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[SQL Server]]></category>

		<guid isPermaLink="false">http://blog.nkadesign.com/?p=433</guid>
		<description><![CDATA[When you start building an Access application, it&#8217;s tempting to just think about today&#8217;s problem and not worry at all about the future. If your application is successful, people will want more out of it and, over time, you&#8217;ll be faced with the task of moving the back-end database to a more robust system like [...]]]></description>
		<wfw:commentRss>http://blog.nkadesign.com/2009/access-building-upsizable-applications/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
