<?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>Edwin M SarmientoMaking a fool out of MSDB &#8211; Edwin M Sarmiento</title>
	<atom:link href="https://www.edwinmsarmiento.com/making-a-fool-out-of-msdb/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.edwinmsarmiento.com</link>
	<description>Intentional Excellence</description>
	<lastBuildDate>Mon, 13 Apr 2026 21:00:49 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
<site xmlns="com-wordpress:feed-additions:1">84283043</site>		<item>
		<title>Making a fool out of MSDB</title>
		<link>https://www.edwinmsarmiento.com/making-a-fool-out-of-msdb/</link>
		<comments>https://www.edwinmsarmiento.com/making-a-fool-out-of-msdb/#respond</comments>
		<pubDate>Wed, 26 Sep 2007 11:20:00 +0000</pubDate>
		<dc:creator>Edwin M Sarmiento</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">http://bassplayerdoc.wordpress.com/2007/09/26/making-a-fool-out-of-msdb</guid>

				<description><![CDATA[I was restoring a SQL Server instance on a different server for DR purposes &#8211; including system databases. What I have overlooked was the fact that restoring the msdb database would mean keeping the existing settings of the old instance into the new one. While I was trying to delete the database maintenance plans and [&#8230;]]]></description>
					<content:encoded><![CDATA[<img width="512" height="512" src="https://www.edwinmsarmiento.com/wp-content/uploads/2015/10/database_icon.png" class="featured-image wp-post-image" alt="" srcset="https://www.edwinmsarmiento.com/wp-content/uploads/2015/10/database_icon.png 512w, https://www.edwinmsarmiento.com/wp-content/uploads/2015/10/database_icon-150x150.png 150w, https://www.edwinmsarmiento.com/wp-content/uploads/2015/10/database_icon-300x300.png 300w, https://www.edwinmsarmiento.com/wp-content/uploads/2015/10/database_icon-35x35.png 35w, https://www.edwinmsarmiento.com/wp-content/uploads/2015/10/database_icon-400x400.png 400w, https://www.edwinmsarmiento.com/wp-content/uploads/2015/10/database_icon-82x82.png 82w" sizes="(max-width: 512px) 100vw, 512px" /><p>I was restoring a SQL Server instance on a different server for DR purposes &#8211; including system databases. What I have overlooked was the fact that restoring the <strong><span style="font-size: 85%;">msdb</span></strong> database would mean keeping the existing settings of the old instance into the new one. While I was trying to delete the database maintenance plans and the jobs, I kept getting an MSX-related error which prevented me from deleting the jobs. I looked at the jobs by running the <strong><span style="font-size: 85%;">sp_help_job</span></strong> system stored procedure and found out that the originating_server column happens to be the name of my old SQL Server instance. This was the primary reason why I could not delete the jobs either from Enterprise Manager or running the <strong><span style="font-size: 85%;">sp_delete_job</span></strong> system stored procedure.</p>
<p>To workaround that issue, I simply modified the <strong>originating_server </strong>column of the sysjobs table to the name of the current instance. After that, I was able to delete the database maintenance plans and the jobs. Now, my server is ready for DR. Log shipping configuration is the next thing to do.</p>
<div class="blogger-post-footer"><img alt="" width="1" height="1" /></div>
]]></content:encoded>
			

		<wfw:commentRss>https://www.edwinmsarmiento.com/making-a-fool-out-of-msdb/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
				<post-id xmlns="com-wordpress:feed-additions:1">679</post-id>	</item>
	</channel>
</rss>