Re: Schema Includes Another Schema

This works in SQL Server 2005 using the xsd:import production in your
TradingPartnerProvider.xsd and TradingPartnerSubmitter.xsd. SQL Server uses
XML schema collections, so they all live in the same XML schema collection.
The requirement is that TradingPartnerCommon.xsd must be cataloged first, or
all of the XML schemas must be added to the XML Schema Collection in one
large XML variable or literal schema (string).

Cheers,
Bob Beauchemin
http://www.SQLskills.com/blogs/bobb


"Neal Walters" <NealWalters@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:56B69EC6-4E66-4D05-B174-445B2BFC8B70@xxxxxxxxxxxxxxxx
I would like to build a schema with Biztalk, then use to define as an XML
column.

The trick is that I want to use nested schemas. For example, I want to
create a schema called TradingPartnerCommon.xsd, then include that in two
other schemas: 1) TradingPartnerProvider.xsd and 2)
TradingPartnerSubmitter.xsd. This will allow me to enforce some
commonality
between different types of TradingPartners.

I know in the past from using Stylus Studio, that other products outside
of
Biztalk have problems finding the source for the second schema.

I'm guessing this isn't allowed. Any ideas though?

Thanks,
Neal Walters
http://Biztalk-Training.com





.

Relevant Pages

  • Re: Upsizing from access: a couple questions
    ... Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) ... so I imported both the data and schema via DTS. ... > The access DB is running on a production site. ... Do I need to get rid of all the identity columns (just ...
    (microsoft.public.sqlserver.dts)
  • Re: schema validation
    ... Kent Tegels wrote: ... Any inserts into TableData need to be validated based on a schema in TableSchema. ... Just put all of the appropriate schemas into an XML schema collection and declare TableData.Data as XML. ... SQL Server will then validate the XML based on schema elements that apply for the indicated namespace. ...
    (microsoft.public.sqlserver.xml)
  • Re: xsd:dateTime and sqltypes:datetime validations differ. Any idea why? Please help.
    ... I know it's bad combination but I am quite SQL guru with a lot of experience, so it's good experience and I understand data well. ... the SQL datetime and smalldatetime types do not have time zones. ... DROP XML SCHEMA COLLECTION TimeTest ... CREATE XML SCHEMA COLLECTION TimeTest ...
    (microsoft.public.sqlserver.xml)
  • Re: schema validation
    ... Any inserts into TableData need to be validated based on a schema in TableSchema. ... Just put all of the appropriate schemas into an XML schema collection and declare TableData.Data as XML. ... SQL Server will then validate the XML based on schema elements that apply for the indicated namespace. ...
    (microsoft.public.sqlserver.xml)
  • Re: Having problems with Typed Xml
    ... we require a timezone on the value. ... > 2- I've defined an Xml Schema Collection ... > Trying the here above context raised the followings error ...
    (microsoft.public.sqlserver.xml)