<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;AkIBSHc9fSp7ImA9WhRRFE4.&quot;"><id>tag:blogger.com,1999:blog-2121111794466979185</id><updated>2011-11-27T18:02:39.965-06:00</updated><title>Yet Another SQL Server Blog</title><subtitle type="html" /><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://yassb.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://yassb.blogspot.com/" /><author><name>M. W. Albert</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://1.bp.blogspot.com/_pYcsI1Mo7Y8/S3qh8ZT7UFI/AAAAAAAAAAM/SyL_YKdYGM8/S220/AIbEiAIAAABDCIWjgsLstP-SbSILdmNhcmRfcGhvdG8qKDhlNGZjY2QwODgzNTZkOGEyZjU1YzZlZGRjODhiZDcwNTdjMWY3OTEwAQKWF-EbKnoLrE8MsqGEUsuxFUyi.jpeg" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>2</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/YetAnotherSqlServerBlog" /><feedburner:info uri="yetanothersqlserverblog" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><entry gd:etag="W/&quot;C0UEQ38yeSp7ImA9WxBVFUk.&quot;"><id>tag:blogger.com,1999:blog-2121111794466979185.post-2794149838011451200</id><published>2010-02-18T19:00:00.000-06:00</published><updated>2010-02-18T19:00:02.191-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-02-18T19:00:02.191-06:00</app:edited><title>SQL Server maintenance solution</title><link rel="replies" type="application/atom+xml" href="http://yassb.blogspot.com/feeds/2794149838011451200/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://yassb.blogspot.com/2010/02/sql-server-maintenance-solution.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2121111794466979185/posts/default/2794149838011451200?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2121111794466979185/posts/default/2794149838011451200?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/YetAnotherSqlServerBlog/~3/R-oPb8asqJo/sql-server-maintenance-solution.html" title="SQL Server maintenance solution" /><author><name>M. W. Albert</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://1.bp.blogspot.com/_pYcsI1Mo7Y8/S3qh8ZT7UFI/AAAAAAAAAAM/SyL_YKdYGM8/S220/AIbEiAIAAABDCIWjgsLstP-SbSILdmNhcmRfcGhvdG8qKDhlNGZjY2QwODgzNTZkOGEyZjU1YzZlZGRjODhiZDcwNTdjMWY3OTEwAQKWF-EbKnoLrE8MsqGEUsuxFUyi.jpeg" /></author><thr:total>0</thr:total><content type="html">I've become a big fan of Ola Hallengren's SQL Server 2005 and 2008 database maintenance solution since I discovered it a few months ago. As anyone that has delved very far into the Reorganize and Rebuild Indexes tasks in SQL 2005/2008 maintenance plans knows, they couldn't exactly be described as 'sophisticated'. The tasks do not take the existing fragmentation level in the indexes into account -
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/bLrM1HdStKVqyXnAKsOdGoRGk6g/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/bLrM1HdStKVqyXnAKsOdGoRGk6g/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/bLrM1HdStKVqyXnAKsOdGoRGk6g/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/bLrM1HdStKVqyXnAKsOdGoRGk6g/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/YetAnotherSqlServerBlog/~4/R-oPb8asqJo" height="1" width="1"/&gt;</content><feedburner:origLink>http://yassb.blogspot.com/2010/02/sql-server-maintenance-solution.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkMEQXs9eSp7ImA9WxBVE0s.&quot;"><id>tag:blogger.com,1999:blog-2121111794466979185.post-4658469826111684785</id><published>2010-02-16T19:00:00.000-06:00</published><updated>2010-02-16T19:00:00.561-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-02-16T19:00:00.561-06:00</app:edited><title>Cloned server problem</title><link rel="replies" type="application/atom+xml" href="http://yassb.blogspot.com/feeds/4658469826111684785/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://yassb.blogspot.com/2010/02/cloned-server-problem.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2121111794466979185/posts/default/4658469826111684785?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2121111794466979185/posts/default/4658469826111684785?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/YetAnotherSqlServerBlog/~3/Rs9t-avF4VI/cloned-server-problem.html" title="Cloned server problem" /><author><name>M. W. Albert</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://1.bp.blogspot.com/_pYcsI1Mo7Y8/S3qh8ZT7UFI/AAAAAAAAAAM/SyL_YKdYGM8/S220/AIbEiAIAAABDCIWjgsLstP-SbSILdmNhcmRfcGhvdG8qKDhlNGZjY2QwODgzNTZkOGEyZjU1YzZlZGRjODhiZDcwNTdjMWY3OTEwAQKWF-EbKnoLrE8MsqGEUsuxFUyi.jpeg" /></author><thr:total>0</thr:total><content type="html">I ran into an interesting problem the other day with a SQL Server on a virtual machine that was a clone of another machine. My co-workers had received a request for another virtual machine that had the same data on it as an older, test server for use in production. So, rather than build a new machine from scratch and backup/restore the test data to it, they simply cloned the virtual machine and 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/3x1henPRNiuzWtU9w9FialXmBMg/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/3x1henPRNiuzWtU9w9FialXmBMg/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/3x1henPRNiuzWtU9w9FialXmBMg/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/3x1henPRNiuzWtU9w9FialXmBMg/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/YetAnotherSqlServerBlog/~4/Rs9t-avF4VI" height="1" width="1"/&gt;</content><feedburner:origLink>http://yassb.blogspot.com/2010/02/cloned-server-problem.html</feedburner:origLink></entry></feed>

