<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/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>Importing an existing XML schema into SQL Server 2005</title><link>http://blogs.msdn.com/denisruc/archive/2006/04/18/578671.aspx</link><description>In my last post I addressed the issue of non deterministic content models, which can be valid with respect to the W3C’s standards, but which are always rejected by SQL Server 2005. There are a few other XSD features that SQL Server 2005 doesn’t support.</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Importing an existing XML schema into SQL Server 2005</title><link>http://blogs.msdn.com/denisruc/archive/2006/04/18/578671.aspx#579008</link><pubDate>Wed, 19 Apr 2006 17:16:03 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:579008</guid><dc:creator>Henry Boehlert</dc:creator><description>Great post, I've been looking for a concise description like this since for quite some time.&lt;br&gt;&lt;br&gt;I already pursued an approach using a .NET function but due to security constraints this did not become an easily applicable solution.&lt;br&gt;&lt;br&gt;One little &amp;quot;add&amp;quot;: key and keyref need to be removed as well, unless this restriction was lifted in SP1 (which I doubt)</description></item><item><title>re: Importing an existing XML schema into SQL Server 2005</title><link>http://blogs.msdn.com/denisruc/archive/2006/04/18/578671.aspx#579190</link><pubDate>Wed, 19 Apr 2006 21:10:05 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:579190</guid><dc:creator>denisruc</dc:creator><description>Thanks for the comment Henry. You are absolutely right, xsd:key and xsd:keyref nodes would have to be removed as well. And there are no plans that I know of to add support for those in the near future. &lt;br&gt;&lt;br&gt;As for SP1 it should be available shortly and I'll probably write a post about the improvements that we made to XML datatype. </description></item><item><title>Download SP1 today!</title><link>http://blogs.msdn.com/denisruc/archive/2006/04/18/578671.aspx#580290</link><pubDate>Fri, 21 Apr 2006 04:48:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:580290</guid><dc:creator>Typed XML in SQL Server 2005</dc:creator><description>&lt;br&gt;Yesterday we released our first Service Pack for SQL Server 2005. You might remember a while back I...</description></item><item><title>Check Out Denis Ruckebusch's Blog</title><link>http://blogs.msdn.com/denisruc/archive/2006/04/18/578671.aspx#582456</link><pubDate>Tue, 25 Apr 2006 00:39:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:582456</guid><dc:creator>SQL Programmability &amp; API Development Team Blog</dc:creator><description>I'm adding a link in the sidebar to Denis Ruckebusch's blog. Denis is one of our testers for the XML...</description></item><item><title>Importing the Microsoft Office 2003 schemas into the database</title><link>http://blogs.msdn.com/denisruc/archive/2006/04/18/578671.aspx#588679</link><pubDate>Wed, 03 May 2006 00:40:41 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:588679</guid><dc:creator>Typed XML in SQL Server 2005</dc:creator><description>As promised earlier I'm going to give you an example&amp;amp;amp;nbsp;using a&amp;amp;amp;nbsp;real-world schema. I've chosen...</description></item><item><title>Problem with sp_xml_PrepareDocument after installing SP1 of SQL2005</title><link>http://blogs.msdn.com/denisruc/archive/2006/04/18/578671.aspx#791097</link><pubDate>Wed, 04 Oct 2006 20:30:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:791097</guid><dc:creator>Waldemar</dc:creator><description>&lt;p&gt;I am calling sp_xml_PrepareDocument from a VS.NEt app against SQL Server 2005 and It worked fine till I installed SP1.&lt;/p&gt;
&lt;p&gt;I got the following XML and sent this command not from the client but from sql management studio.&lt;/p&gt;
&lt;p&gt;DECLARE @hdoc int&lt;/p&gt;
&lt;p&gt;DECLARE @doc varchar(1000)&lt;/p&gt;
&lt;p&gt;SET @doc =&lt;/p&gt;
&lt;p&gt;'&amp;lt;?xml version=&amp;quot;1.0&amp;quot; encoding=&amp;quot;utf-16&amp;quot;?&amp;gt;&lt;/p&gt;
&lt;p&gt;&amp;lt;Keys xmlns:xsi=&amp;quot;&lt;a rel="nofollow" target="_new" href="http://www.w3.org/2001/XMLSchema-instance&amp;quot;"&gt;http://www.w3.org/2001/XMLSchema-instance&amp;quot;&lt;/a&gt; xmlns:xsd=&amp;quot;&lt;a rel="nofollow" target="_new" href="http://www.w3.org/2001/XMLSchema&amp;quot;&amp;gt;"&gt;http://www.w3.org/2001/XMLSchema&amp;quot;&amp;gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt; &amp;nbsp;&amp;lt;Key ID=&amp;quot;26&amp;quot; Code=&amp;quot;1000149&amp;quot; /&amp;gt;&lt;/p&gt;
&lt;p&gt;&amp;lt;/Keys&amp;gt;'&lt;/p&gt;
&lt;p&gt;EXEC sp_xml_preparedocument @hdoc OUTPUT, @doc&lt;/p&gt;
&lt;p&gt;If I change @Doc to nvarchar it works, I did it on the client too but this time it does not work.&lt;/p&gt;
&lt;p&gt;Any suggestions?&lt;/p&gt;
</description></item><item><title>re: Importing an existing XML schema into SQL Server 2005</title><link>http://blogs.msdn.com/denisruc/archive/2006/04/18/578671.aspx#1490119</link><pubDate>Thu, 18 Jan 2007 22:40:35 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1490119</guid><dc:creator>Steve</dc:creator><description>&lt;p&gt;Great article. I just discovered your site and immediately set it as a favorite. &lt;/p&gt;
&lt;p&gt;I'm trying to find how I might be able to replace a schema already in a schema collection. I could easily just add the revised schema to the collection and give it a slightly different namespace but I don't want to get sloppy. Any suggestions? &lt;/p&gt;
&lt;p&gt;Cheers.&lt;/p&gt;
&lt;p&gt;Steve Campos&lt;/p&gt;
</description></item><item><title>re: Importing an existing XML schema into SQL Server 2005</title><link>http://blogs.msdn.com/denisruc/archive/2006/04/18/578671.aspx#1519882</link><pubDate>Wed, 24 Jan 2007 09:28:39 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1519882</guid><dc:creator>denisruc</dc:creator><description>&lt;p&gt;Steve,&lt;/p&gt;
&lt;p&gt;Unfortunately for now we don't support removing or replacing schema components, only adding them.&lt;/p&gt;
&lt;p&gt;You can create a new collection for your new schema and then retype all the columns constrained by the old collection (with ALTER TABLE ALTER COLUMN)&lt;/p&gt;
</description></item><item><title>re: Importing an existing XML schema into SQL Server 2005</title><link>http://blogs.msdn.com/denisruc/archive/2006/04/18/578671.aspx#2015467</link><pubDate>Tue, 03 Apr 2007 05:27:52 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2015467</guid><dc:creator>Terry Aney</dc:creator><description>&lt;p&gt;What is the performance hit of dropping a schema collection (alter table alter column) and then re-adding it?&lt;/p&gt;
&lt;p&gt;Additionally, if I have an Xml index set up, I have to remove that first as well right? &amp;nbsp;I would assume this performance hit would be bad?&lt;/p&gt;
</description></item><item><title>Error creating XML Schema Collections | keyongtech</title><link>http://blogs.msdn.com/denisruc/archive/2006/04/18/578671.aspx#9338223</link><pubDate>Sun, 18 Jan 2009 19:45:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9338223</guid><dc:creator>Error creating XML Schema Collections | keyongtech</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.keyongtech.com/2168269-error-creating-xml-schema-collections"&gt;http://www.keyongtech.com/2168269-error-creating-xml-schema-collections&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>Schema collection and xs:include | keyongtech</title><link>http://blogs.msdn.com/denisruc/archive/2006/04/18/578671.aspx#9362152</link><pubDate>Thu, 22 Jan 2009 06:35:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9362152</guid><dc:creator>Schema collection and xs:include | keyongtech</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.keyongtech.com/2256511-schema-collection-and-xs-include"&gt;http://www.keyongtech.com/2256511-schema-collection-and-xs-include&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>sql2005 &amp;amp; schemaXML multiples - Page 3 | hilpers</title><link>http://blogs.msdn.com/denisruc/archive/2006/04/18/578671.aspx#9368188</link><pubDate>Thu, 22 Jan 2009 18:06:01 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9368188</guid><dc:creator>sql2005 &amp;amp; schemaXML multiples - Page 3 | hilpers</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.hilpers.fr/919210-sql2005-and-schemaxml-multiples/3"&gt;http://www.hilpers.fr/919210-sql2005-and-schemaxml-multiples/3&lt;/a&gt;&lt;/p&gt;
</description></item><item><title> Typed XML in SQL Server 2005 Importing an existing XML schema into | Paid Surveys</title><link>http://blogs.msdn.com/denisruc/archive/2006/04/18/578671.aspx#9683999</link><pubDate>Tue, 02 Jun 2009 10:01:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9683999</guid><dc:creator> Typed XML in SQL Server 2005 Importing an existing XML schema into | Paid Surveys</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://paidsurveyshub.info/story.php?id=74810"&gt;http://paidsurveyshub.info/story.php?id=74810&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>