<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://bloggingabout.net/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Search results matching tags 'Microsoft' and 'SQL 2005'</title><link>http://bloggingabout.net/search/SearchResults.aspx?a=1&amp;o=DateDescending&amp;tag=Microsoft,SQL+2005&amp;orTags=0</link><description>Search results matching tags 'Microsoft' and 'SQL 2005'</description><dc:language>en-US</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator><item><title>No Identity Specification on DB Copy in SQL Mgmt Studio?</title><link>http://bloggingabout.net/blogs/egiardina/archive/2007/08/09/no-identity-specification-on-db-copy-in-sql-mgmt-studio.aspx</link><pubDate>Thu, 09 Aug 2007 18:55:00 GMT</pubDate><guid isPermaLink="false">813b6dfd-644e-4573-a816-eebab56ba0d0:336699</guid><dc:creator>Richthofen</dc:creator><description>&lt;p&gt;So slowly but surely some of our databases are making it from SQL Server 2000 to SQL Server 2005. In that process, some of our databases are moved using the quick &amp;#39;copy&amp;#39; method.&amp;nbsp; Simply right click on the DB in SQL Management Studio, go to tasks, select Copy Database. &lt;br /&gt;&lt;/p&gt;&lt;p&gt;However, on my setup:&lt;/p&gt;&lt;p&gt;Microsoft SQL Server Management Studio&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;9.00.1399.00&lt;br /&gt;Microsoft Analysis Services Client Tools&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;2005.090.1399.00&lt;br /&gt;Microsoft Data Access Components (MDAC)&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)&lt;br /&gt;Microsoft MSXML&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;2.6 3.0 4.0 5.0 6.0 &lt;br /&gt;Microsoft Internet Explorer&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;7.0.5730.11&lt;br /&gt;Microsoft .NET Framework&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;2.0.50727.832&lt;br /&gt;Operating System&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;5.1.2600&lt;/p&gt;&lt;p&gt;When moving from a SQL 2000 -&amp;gt; 2005 copy, the new database fails to maintain the &amp;#39;identity specification&amp;#39; as YES on the primary keys of my tables. Subsequently, I had to manually add the identity spec. back on about 10 tables. Lame!&lt;/p&gt;&lt;p&gt;I wanted to report this bug to Microsoft, but figuring out how to report a bug is like pulling teeth! There&amp;#39;s no general public bug submission form; you can go through their &amp;#39;connect&amp;#39; program but its a huge pain in the ass. If they want to write better software, Microsoft should at least give me a bug report form. &lt;br /&gt;&lt;br /&gt;&amp;nbsp;&lt;/p&gt;</description></item></channel></rss>