<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: SQL Server 2005 Problems and Solutions</title>
	<atom:link href="http://brennan.offwhite.net/blog/2006/07/31/sql-server-2005-problems-and-solutions/feed/" rel="self" type="application/rss+xml" />
	<link>http://brennan.offwhite.net/blog/2006/07/31/sql-server-2005-problems-and-solutions/</link>
	<description>My Experiences with Software Development</description>
	<pubDate>Sat, 05 Jul 2008 10:13:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Ed Hartmann</title>
		<link>http://brennan.offwhite.net/blog/2006/07/31/sql-server-2005-problems-and-solutions/#comment-19105</link>
		<dc:creator>Ed Hartmann</dc:creator>
		<pubDate>Sat, 23 Jun 2007 19:25:15 +0000</pubDate>
		<guid isPermaLink="false">http://brennan.offwhite.net/blog/2006/07/31/sql-server-2005-problems-and-solutions/#comment-19105</guid>
		<description>I came across your blog while searching for information about error 15517. I teach SQL Server 2005 classes at Bellevue Community College in Bellevue, WA. My students restored a database (locally) that I had backed up on my workstation. They tried to use a UDF that I had created, and the error appeared. I solved the problem by having the students run sp_changedbowner 'sa'.  The error probably was probably due to the fact that the Windows account that owned the database had a different SID on each workstation. The sa account has the same SID (0x01) on all SQL Server installations.</description>
		<content:encoded><![CDATA[<p>I came across your blog while searching for information about error 15517. I teach SQL Server 2005 classes at Bellevue Community College in Bellevue, WA. My students restored a database (locally) that I had backed up on my workstation. They tried to use a UDF that I had created, and the error appeared. I solved the problem by having the students run sp_changedbowner 'sa'.  The error probably was probably due to the fact that the Windows account that owned the database had a different SID on each workstation. The sa account has the same SID (0x01) on all SQL Server installations.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
