sql rowcount: bol

Showing posts with label bol. Show all posts

Sunday, March 11, 2012

[SQL 2005] XQuery xs:NOTATION

I thought I read in BOL that SQL 2K5's XQuery implementation does not
support the XML Schema xs:NOTATION datatype; but I'm having a hard time
finding that page again. I was able to locate a page in BOL
(http://msdn2.microsoft.com/en-us/library/ms191231.aspx) that indicates type
casting to/from xs:NOTATION is not supported, but need to know is
xs:NOTATION actually supported at all? Any references to this information
(one way or the other) is appreciated.
Thanks!Hi Mike
On the page you posted
http://msdn2.microsoft.com/en-us/library/ms191231.aspx :
"xs:NOTATION and the fully ordered subtypes of duration,
xdt:yearMonthDuration and xdt:dayTimeDuration, are not supported. As a
result, casting to or from these types is not supported."
On http://msdn2.microsoft.com/pt-br/library/ms189547.aspx
"Constructors are supported for base and derived atomic XSD types. However,
the subtypes of xs:duration, which includes xdt:yearMonthDuration and
xdt:dayTimeDuration, and xs:QName, xs:NMTOKEN, and xs:NOTATION are not
supported. User-defined atomic types that are available in the associated
schema collections are also available, provided they are directly or
indirectly derived from the following types."
John
"Mike C#" wrote:
> I thought I read in BOL that SQL 2K5's XQuery implementation does not
> support the XML Schema xs:NOTATION datatype; but I'm having a hard time
> finding that page again. I was able to locate a page in BOL
> (http://msdn2.microsoft.com/en-us/library/ms191231.aspx) that indicates type
> casting to/from xs:NOTATION is not supported, but need to know is
> xs:NOTATION actually supported at all? Any references to this information
> (one way or the other) is appreciated.
> Thanks!
>
>|||"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:A04FBA1C-8FB5-4461-83D3-201B858C672F@.microsoft.com...
> Hi Mike
> On the page you posted
> http://msdn2.microsoft.com/en-us/library/ms191231.aspx :
> "xs:NOTATION and the fully ordered subtypes of duration,
> xdt:yearMonthDuration and xdt:dayTimeDuration, are not supported. As a
> result, casting to or from these types is not supported."
Thanks, that seems to indicate xs:NOTATION is not supported at all. The
fact that xs:NOTATION is included in the chart at the top of that page seems
to contradict that wording though...
> On http://msdn2.microsoft.com/pt-br/library/ms189547.aspx
> "Constructors are supported for base and derived atomic XSD types.
> However,
> the subtypes of xs:duration, which includes xdt:yearMonthDuration and
> xdt:dayTimeDuration, and xs:QName, xs:NMTOKEN, and xs:NOTATION are not
> supported. User-defined atomic types that are available in the associated
> schema collections are also available, provided they are directly or
> indirectly derived from the following types."
Here's where the confusion comes in - xs:NOTATION is either supported (as a
virtual base type, as indicated on the chart on the first page and alluded
to in the quote from the second page), or it's not supported at all (as
indicated by the wording on the first page).
I assume the statement from the second page doesn't really indicate that
xs:NOTATION itself is not supported, but rather that an xs:NOTATION
constructor is not supported. That's based on the fact that xs:QName *is*
supported (though no constructor), and it's listed in the same sentence
where it says "...are not supported."
Mostly I think I'm just a victim of poor wording. xs:NOTATION constructor
and xs:NOTATION casting are clearly not supported, but is xs:NOTATION itself
(even as a virtual base type) supported or not?|||Hi Mike
I think overall if you add everything up then you have to say there is no
support at all. There is no constructor so you can't create anything of that
type, you can not cast to or from so even if you had something of that type
you can't do much with it.
Have you tried using it?
John
"Mike C#" wrote:
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:A04FBA1C-8FB5-4461-83D3-201B858C672F@.microsoft.com...
> > Hi Mike
> >
> > On the page you posted
> > http://msdn2.microsoft.com/en-us/library/ms191231.aspx :
> >
> > "xs:NOTATION and the fully ordered subtypes of duration,
> > xdt:yearMonthDuration and xdt:dayTimeDuration, are not supported. As a
> > result, casting to or from these types is not supported."
> Thanks, that seems to indicate xs:NOTATION is not supported at all. The
> fact that xs:NOTATION is included in the chart at the top of that page seems
> to contradict that wording though...
> > On http://msdn2.microsoft.com/pt-br/library/ms189547.aspx
> >
> > "Constructors are supported for base and derived atomic XSD types.
> > However,
> > the subtypes of xs:duration, which includes xdt:yearMonthDuration and
> > xdt:dayTimeDuration, and xs:QName, xs:NMTOKEN, and xs:NOTATION are not
> > supported. User-defined atomic types that are available in the associated
> > schema collections are also available, provided they are directly or
> > indirectly derived from the following types."
> Here's where the confusion comes in - xs:NOTATION is either supported (as a
> virtual base type, as indicated on the chart on the first page and alluded
> to in the quote from the second page), or it's not supported at all (as
> indicated by the wording on the first page).
> I assume the statement from the second page doesn't really indicate that
> xs:NOTATION itself is not supported, but rather that an xs:NOTATION
> constructor is not supported. That's based on the fact that xs:QName *is*
> supported (though no constructor), and it's listed in the same sentence
> where it says "...are not supported."
> Mostly I think I'm just a victim of poor wording. xs:NOTATION constructor
> and xs:NOTATION casting are clearly not supported, but is xs:NOTATION itself
> (even as a virtual base type) supported or not?
>
>|||"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:AC29C43A-7507-48AF-A419-3015A4654597@.microsoft.com...
> Hi Mike
> I think overall if you add everything up then you have to say there is no
> support at all. There is no constructor so you can't create anything of
> that
> type, you can not cast to or from so even if you had something of that
> type
> you can't do much with it.
> Have you tried using it?
Consider xs:QName: ( no constructor for xs:QName + no casting to or from an
xs:QName from any other type ) != no support at all. xs:QName is definitely
supported.
I haven't tried using xs:NOTATION directly, since the chart indicates it's a
"virtual base type". Presumably other types can be created from it. I
figured the good folks from Microsoft who visit these newsgroups might be
able to shed some light on how it might be used at all if it is supported as
a "virtual base type", or explain the apparent discrepancy in the
documentation if it's not supported at all.
Thanks.|||"Mike C#" <xyz@.xyz.com> wrote in message
news:uzrl9$HHHHA.3872@.TK2MSFTNGP06.phx.gbl...
>> Have you tried using it?
> Consider xs:QName: ( no constructor for xs:QName + no casting to or from
> an xs:QName from any other type ) != no support at all. xs:QName is
> definitely supported.
> I haven't tried using xs:NOTATION directly, since the chart indicates it's
> a "virtual base type". Presumably other types can be created from it. I
> figured the good folks from Microsoft who visit these newsgroups might be
> able to shed some light on how it might be used at all if it is supported
> as a "virtual base type", or explain the apparent discrepancy in the
> documentation if it's not supported at all.
>
I just ran a simple test for xs:NOTATION, and the result was SQL giving me
the error message "NOTATION not supported". So it looks like it doesn't
support xs:NOTATION at all. Someone at MS should fix that chart on the
XQuery datatypes casting page.
Thanks for the help!|||Hi Mike
The chart shows casting between QNs so it would indicate some support! It
may be interesting to see what happens if you try to construct one!!
You could try sending feedback on this using the contact us option at the
bottom of the page.
John
"Mike C#" wrote:
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:AC29C43A-7507-48AF-A419-3015A4654597@.microsoft.com...
> > Hi Mike
> >
> > I think overall if you add everything up then you have to say there is no
> > support at all. There is no constructor so you can't create anything of
> > that
> > type, you can not cast to or from so even if you had something of that
> > type
> > you can't do much with it.
> >
> > Have you tried using it?
> Consider xs:QName: ( no constructor for xs:QName + no casting to or from an
> xs:QName from any other type ) != no support at all. xs:QName is definitely
> supported.
> I haven't tried using xs:NOTATION directly, since the chart indicates it's a
> "virtual base type". Presumably other types can be created from it. I
> figured the good folks from Microsoft who visit these newsgroups might be
> able to shed some light on how it might be used at all if it is supported as
> a "virtual base type", or explain the apparent discrepancy in the
> documentation if it's not supported at all.
> Thanks.
>
>|||"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:7C916F7A-ED18-46E3-86F4-4E5B2E93D1A5@.microsoft.com...
> Hi Mike
> The chart shows casting between QNs so it would indicate some support! It
> may be interesting to see what happens if you try to construct one!!
> You could try sending feedback on this using the contact us option at the
> bottom of the page.
>
Hi John
QN's don't have a constructor function per se, but there is an F&O function
to create a QN. The QN casting is strictly QN to QN. The xs:NOTATION
doesn't even work with the "instance of" operator (which was my test), and
it comes back with the error message stating explicitly that no support for
xs:NOTATION exists, so that's what I'm going with :)
Thanks|||The first thing to test is, if the type is supported in XML Schema
collections... and it is not.
CREATE XML SCHEMA COLLECTION SCX AS
N'<xsd:schema targetNamespace="urn:example/customer"
xmlns:e="urn:example/customer"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<xsd:element name="buys" type="xsd:NOTATION"/>
</xsd:schema>'
returns
Msg 9337, Level 16, State 1, Line 1
The XML Schema type 'NOTATION' is not supported.
Since schema does not support the type, XQuery does not either.
If this type is important for your scenario, please file a bug report under
http://connect.microsoft.com/sqlserver
Thanks
Michael
"Mike C#" <xyz@.xyz.com> wrote in message
news:%23RoXrrTHHHA.1816@.TK2MSFTNGP06.phx.gbl...
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:7C916F7A-ED18-46E3-86F4-4E5B2E93D1A5@.microsoft.com...
>> Hi Mike
>> The chart shows casting between QNs so it would indicate some support! It
>> may be interesting to see what happens if you try to construct one!!
>> You could try sending feedback on this using the contact us option at the
>> bottom of the page.
> Hi John
> QN's don't have a constructor function per se, but there is an F&O
> function to create a QN. The QN casting is strictly QN to QN. The
> xs:NOTATION doesn't even work with the "instance of" operator (which was
> my test), and it comes back with the error message stating explicitly that
> no support for xs:NOTATION exists, so that's what I'm going with :)
> Thanks
>|||I can work around that limitation for now. It would be nice if they could
refresh the documentation on it to get rid of xs:NOTATION from the chart and
state a little more clearly that it's not supported. Right now the
statement that it's not supported is combined with a couple of other items
that are supported in various fashions, which leads to having to do tests
like this to determine if it actually is supported or not.
Thanks.
"Michael Rys [MSFT]" <mrys@.online.microsoft.com> wrote in message
news:eFSlFP8HHHA.1248@.TK2MSFTNGP03.phx.gbl...
> The first thing to test is, if the type is supported in XML Schema
> collections... and it is not.
> CREATE XML SCHEMA COLLECTION SCX AS
> N'<xsd:schema targetNamespace="urn:example/customer"
> xmlns:e="urn:example/customer"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> elementFormDefault="qualified">
> <xsd:element name="buys" type="xsd:NOTATION"/>
> </xsd:schema>'
> returns
> Msg 9337, Level 16, State 1, Line 1
> The XML Schema type 'NOTATION' is not supported.
> Since schema does not support the type, XQuery does not either.
> If this type is important for your scenario, please file a bug report
> under http://connect.microsoft.com/sqlserver
> Thanks
> Michael
> "Mike C#" <xyz@.xyz.com> wrote in message
> news:%23RoXrrTHHHA.1816@.TK2MSFTNGP06.phx.gbl...
>> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
>> news:7C916F7A-ED18-46E3-86F4-4E5B2E93D1A5@.microsoft.com...
>> Hi Mike
>> The chart shows casting between QNs so it would indicate some support!
>> It
>> may be interesting to see what happens if you try to construct one!!
>> You could try sending feedback on this using the contact us option at
>> the
>> bottom of the page.
>>
>> Hi John
>> QN's don't have a constructor function per se, but there is an F&O
>> function to create a QN. The QN casting is strictly QN to QN. The
>> xs:NOTATION doesn't even work with the "instance of" operator (which was
>> my test), and it comes back with the error message stating explicitly
>> that no support for xs:NOTATION exists, so that's what I'm going with :)
>> Thanks
>|||Hi Mike
If you find the limitation for <xsd:limitation>,pls let me know at
rohiniraj@.rediffmail.com
Im also struggling in that only.
Also if you find the limitation for
XML schema components can have an ID attribute, but SQL Server does not
store these value
pls tell me.
Thanks in advance.|||These limitations should all be documented in Books Online.
I know that we document that we do not save the ID attribute...
If any of the existing limitations are a problem, please file a bug
report/feature request at
http://connect.microsoft.com/sqlserver.
Thanks
Mike
<rohiniraj@.rediffmail.com> wrote in message
news:1166538986.101987.264990@.73g2000cwn.googlegroups.com...
> Hi Mike
> If you find the limitation for <xsd:limitation>,pls let me know at
> rohiniraj@.rediffmail.com
> Im also struggling in that only.
> Also if you find the limitation for
> XML schema components can have an ID attribute, but SQL Server does not
> store these value
> pls tell me.
> Thanks in advance.
>

[SQL 2005] XQuery xs:NOTATION

Thanks|||The first thing to test is, if the type is supported in XML Schema
collections... and it is not.
CREATE XML SCHEMA COLLECTION SCX AS
N'<xsd:schema targetNamespace="urn:example/customer"
xmlns:e="urn:example/customer"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<xsd:element name="buys" type="xsd:NOTATION"/>
</xsd:schema>'
returns
Msg 9337, Level 16, State 1, Line 1
The XML Schema type 'NOTATION' is not supported.
Since schema does not support the type, XQuery does not either.
If this type is important for your scenario, please file a bug report under
http://connect.microsoft.com/sqlserver
Thanks
Michael
"Mike C#" <xyz@.xyz.com> wrote in message
news:%23RoXrrTHHHA.1816@.TK2MSFTNGP06.phx.gbl...
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:7C916F7A-ED18-46E3-86F4-4E5B2E93D1A5@.microsoft.com...
> Hi John
> QN's don't have a constructor function per se, but there is an F&O
> function to create a QN. The QN casting is strictly QN to QN. The
> xs:NOTATION doesn't even work with the "instance of" operator (which was
> my test), and it comes back with the error message stating explicitly that
> no support for xs:NOTATION exists, so that's what I'm going with

> Thanks
>|||Hi Mike
If you find the limitation for <xsd:limitation>,pls let me know at
rohiniraj@.rediffmail.com
Im also struggling in that only.
Also if you find the limitation for
XML schema components can have an ID attribute, but SQL Server does not
store these value
pls tell me.
Thanks in advance.

[SQL 2005] XQuery xs:NOTATION

I thought I read in BOL that SQL 2K5's XQuery implementation does not
support the XML Schema xs:NOTATION datatype; but I'm having a hard time
finding that page again. I was able to locate a page in BOL
(http://msdn2.microsoft.com/en-us/library/ms191231.aspx) that indicates type
casting to/from xs:NOTATION is not supported, but need to know is
xs:NOTATION actually supported at all? Any references to this information
(one way or the other) is appreciated.
Thanks!Hi Mike
On the page you posted
http://msdn2.microsoft.com/en-us/library/ms191231.aspx :
"xs:NOTATION and the fully ordered subtypes of duration,
xdt:yearMonthDuration and xdt:dayTimeDuration, are not supported. As a
result, casting to or from these types is not supported."
On http://msdn2.microsoft.com/pt-br/library/ms189547.aspx
"Constructors are supported for base and derived atomic XSD types. However,
the subtypes of xs:duration, which includes xdt:yearMonthDuration and
xdt:dayTimeDuration, and xs:QName, xs:NMTOKEN, and xs:NOTATION are not
supported. User-defined atomic types that are available in the associated
schema collections are also available, provided they are directly or
indirectly derived from the following types."
John
"Mike C#" wrote:

> I thought I read in BOL that SQL 2K5's XQuery implementation does not
> support the XML Schema xs:NOTATION datatype; but I'm having a hard time
> finding that page again. I was able to locate a page in BOL
> (http://msdn2.microsoft.com/en-us/library/ms191231.aspx) that indicates ty
pe
> casting to/from xs:NOTATION is not supported, but need to know is
> xs:NOTATION actually supported at all? Any references to this information
> (one way or the other) is appreciated.
> Thanks!
>
>|||"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:A04FBA1C-8FB5-4461-83D3-201B858C672F@.microsoft.com...
> Hi Mike
> On the page you posted
> http://msdn2.microsoft.com/en-us/library/ms191231.aspx :
> "xs:NOTATION and the fully ordered subtypes of duration,
> xdt:yearMonthDuration and xdt:dayTimeDuration, are not supported. As a
> result, casting to or from these types is not supported."
Thanks, that seems to indicate xs:NOTATION is not supported at all. The
fact that xs:NOTATION is included in the chart at the top of that page seems
to contradict that wording though...

> On http://msdn2.microsoft.com/pt-br/library/ms189547.aspx
> "Constructors are supported for base and derived atomic XSD types.
> However,
> the subtypes of xs:duration, which includes xdt:yearMonthDuration and
> xdt:dayTimeDuration, and xs:QName, xs:NMTOKEN, and xs:NOTATION are not
> supported. User-defined atomic types that are available in the associated
> schema collections are also available, provided they are directly or
> indirectly derived from the following types."
Here's where the confusion comes in - xs:NOTATION is either supported (as a
virtual base type, as indicated on the chart on the first page and alluded
to in the quote from the second page), or it's not supported at all (as
indicated by the wording on the first page).
I assume the statement from the second page doesn't really indicate that
xs:NOTATION itself is not supported, but rather that an xs:NOTATION
constructor is not supported. That's based on the fact that xs:QName *is*
supported (though no constructor), and it's listed in the same sentence
where it says "...are not supported."
Mostly I think I'm just a victim of poor wording. xs:NOTATION constructor
and xs:NOTATION casting are clearly not supported, but is xs:NOTATION itself
(even as a virtual base type) supported or not?|||Hi Mike
I think overall if you add everything up then you have to say there is no
support at all. There is no constructor so you can't create anything of that
type, you can not cast to or from so even if you had something of that type
you can't do much with it.
Have you tried using it?
John
"Mike C#" wrote:

> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:A04FBA1C-8FB5-4461-83D3-201B858C672F@.microsoft.com...
> Thanks, that seems to indicate xs:NOTATION is not supported at all. The
> fact that xs:NOTATION is included in the chart at the top of that page see
ms
> to contradict that wording though...
>
> Here's where the confusion comes in - xs:NOTATION is either supported (as
a
> virtual base type, as indicated on the chart on the first page and alluded
> to in the quote from the second page), or it's not supported at all (as
> indicated by the wording on the first page).
> I assume the statement from the second page doesn't really indicate that
> xs:NOTATION itself is not supported, but rather that an xs:NOTATION
> constructor is not supported. That's based on the fact that xs:QName *is*
> supported (though no constructor), and it's listed in the same sentence
> where it says "...are not supported."
> Mostly I think I'm just a victim of poor wording. xs:NOTATION constructor
> and xs:NOTATION casting are clearly not supported, but is xs:NOTATION itse
lf
> (even as a virtual base type) supported or not?
>
>|||"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:AC29C43A-7507-48AF-A419-3015A4654597@.microsoft.com...
> Hi Mike
> I think overall if you add everything up then you have to say there is no
> support at all. There is no constructor so you can't create anything of
> that
> type, you can not cast to or from so even if you had something of that
> type
> you can't do much with it.
> Have you tried using it?
Consider xs:QName: ( no constructor for xs:QName + no casting to or from an
xs:QName from any other type ) != no support at all. xs:QName is definitely
supported.
I haven't tried using xs:NOTATION directly, since the chart indicates it's a
"virtual base type". Presumably other types can be created from it. I
figured the good folks from Microsoft who visit these newsgroups might be
able to shed some light on how it might be used at all if it is supported as
a "virtual base type", or explain the apparent discrepancy in the
documentation if it's not supported at all.
Thanks.|||"Mike C#" <xyz@.xyz.com> wrote in message
news:uzrl9$HHHHA.3872@.TK2MSFTNGP06.phx.gbl...
> Consider xs:QName: ( no constructor for xs:QName + no casting to or from
> an xs:QName from any other type ) != no support at all. xs:QName is
> definitely supported.
> I haven't tried using xs:NOTATION directly, since the chart indicates it's
> a "virtual base type". Presumably other types can be created from it. I
> figured the good folks from Microsoft who visit these newsgroups might be
> able to shed some light on how it might be used at all if it is supported
> as a "virtual base type", or explain the apparent discrepancy in the
> documentation if it's not supported at all.
>
I just ran a simple test for xs:NOTATION, and the result was SQL giving me
the error message "NOTATION not supported". So it looks like it doesn't
support xs:NOTATION at all. Someone at MS should fix that chart on the
XQuery datatypes casting page.
Thanks for the help!|||Hi Mike
The chart shows casting between QNs so it would indicate some support! It
may be interesting to see what happens if you try to construct one!!
You could try sending feedback on this using the contact us option at the
bottom of the page.
John
"Mike C#" wrote:

> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:AC29C43A-7507-48AF-A419-3015A4654597@.microsoft.com...
> Consider xs:QName: ( no constructor for xs:QName + no casting to or from
an
> xs:QName from any other type ) != no support at all. xs:QName is definite
ly
> supported.
> I haven't tried using xs:NOTATION directly, since the chart indicates it's
a
> "virtual base type". Presumably other types can be created from it. I
> figured the good folks from Microsoft who visit these newsgroups might be
> able to shed some light on how it might be used at all if it is supported
as
> a "virtual base type", or explain the apparent discrepancy in the
> documentation if it's not supported at all.
> Thanks.
>
>|||"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:7C916F7A-ED18-46E3-86F4-4E5B2E93D1A5@.microsoft.com...
> Hi Mike
> The chart shows casting between QNs so it would indicate some support! It
> may be interesting to see what happens if you try to construct one!!
> You could try sending feedback on this using the contact us option at the
> bottom of the page.
>
Hi John
QN's don't have a constructor function per se, but there is an F&O function
to create a QN. The QN casting is strictly QN to QN. The xs:NOTATION
doesn't even work with the "instance of" operator (which was my test), and
it comes back with the error message stating explicitly that no support for
xs:NOTATION exists, so that's what I'm going with :)
Thanks|||The first thing to test is, if the type is supported in XML Schema
collections... and it is not.
CREATE XML SCHEMA COLLECTION SCX AS
N'<xsd:schema targetNamespace="urn:example/customer"
xmlns:e="urn:example/customer"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<xsd:element name="buys" type="xsd:NOTATION"/>
</xsd:schema>'
returns
Msg 9337, Level 16, State 1, Line 1
The XML Schema type 'NOTATION' is not supported.
Since schema does not support the type, XQuery does not either.
If this type is important for your scenario, please file a bug report under
http://connect.microsoft.com/sqlserver
Thanks
Michael
"Mike C#" <xyz@.xyz.com> wrote in message
news:%23RoXrrTHHHA.1816@.TK2MSFTNGP06.phx.gbl...
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:7C916F7A-ED18-46E3-86F4-4E5B2E93D1A5@.microsoft.com...
> Hi John
> QN's don't have a constructor function per se, but there is an F&O
> function to create a QN. The QN casting is strictly QN to QN. The
> xs:NOTATION doesn't even work with the "instance of" operator (which was
> my test), and it comes back with the error message stating explicitly that
> no support for xs:NOTATION exists, so that's what I'm going with :)
> Thanks
>|||I can work around that limitation for now. It would be nice if they could
refresh the documentation on it to get rid of xs:NOTATION from the chart and
state a little more clearly that it's not supported. Right now the
statement that it's not supported is combined with a couple of other items
that are supported in various fashions, which leads to having to do tests
like this to determine if it actually is supported or not.
Thanks.
"Michael Rys [MSFT]" <mrys@.online.microsoft.com> wrote in message
news:eFSlFP8HHHA.1248@.TK2MSFTNGP03.phx.gbl...
> The first thing to test is, if the type is supported in XML Schema
> collections... and it is not.
> CREATE XML SCHEMA COLLECTION SCX AS
> N'<xsd:schema targetNamespace="urn:example/customer"
> xmlns:e="urn:example/customer"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> elementFormDefault="qualified">
> <xsd:element name="buys" type="xsd:NOTATION"/>
> </xsd:schema>'
> returns
> Msg 9337, Level 16, State 1, Line 1
> The XML Schema type 'NOTATION' is not supported.
> Since schema does not support the type, XQuery does not either.
> If this type is important for your scenario, please file a bug report
> under http://connect.microsoft.com/sqlserver
> Thanks
> Michael
> "Mike C#" <xyz@.xyz.com> wrote in message
> news:%23RoXrrTHHHA.1816@.TK2MSFTNGP06.phx.gbl...
>

[SQL 2005] XQuery xs:NOTATION

Thanks
|||The first thing to test is, if the type is supported in XML Schema
collections... and it is not.
CREATE XML SCHEMA COLLECTION SCX AS
N'<xsd:schema targetNamespace="urn:example/customer"
xmlns:e="urn:example/customer"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<xsd:element name="buys" type="xsd:NOTATION"/>
</xsd:schema>'
returns
Msg 9337, Level 16, State 1, Line 1
The XML Schema type 'NOTATION' is not supported.
Since schema does not support the type, XQuery does not either.
If this type is important for your scenario, please file a bug report under
http://connect.microsoft.com/sqlserver
Thanks
Michael
"Mike C#" <xyz@.xyz.com> wrote in message
news:%23RoXrrTHHHA.1816@.TK2MSFTNGP06.phx.gbl...
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:7C916F7A-ED18-46E3-86F4-4E5B2E93D1A5@.microsoft.com...
> Hi John
> QN's don't have a constructor function per se, but there is an F&O
> function to create a QN. The QN casting is strictly QN to QN. The
> xs:NOTATION doesn't even work with the "instance of" operator (which was
> my test), and it comes back with the error message stating explicitly that
> no support for xs:NOTATION exists, so that's what I'm going with

> Thanks
>
|||I can work around that limitation for now. It would be nice if they could
refresh the documentation on it to get rid of xs:NOTATION from the chart and
state a little more clearly that it's not supported. Right now the
statement that it's not supported is combined with a couple of other items
that are supported in various fashions, which leads to having to do tests
like this to determine if it actually is supported or not.
Thanks.
"Michael Rys [MSFT]" <mrys@.online.microsoft.com> wrote in message
news:eFSlFP8HHHA.1248@.TK2MSFTNGP03.phx.gbl...
> The first thing to test is, if the type is supported in XML Schema
> collections... and it is not.
> CREATE XML SCHEMA COLLECTION SCX AS
> N'<xsd:schema targetNamespace="urn:example/customer"
> xmlns:e="urn:example/customer"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> elementFormDefault="qualified">
> <xsd:element name="buys" type="xsd:NOTATION"/>
> </xsd:schema>'
> returns
> Msg 9337, Level 16, State 1, Line 1
> The XML Schema type 'NOTATION' is not supported.
> Since schema does not support the type, XQuery does not either.
> If this type is important for your scenario, please file a bug report
> under http://connect.microsoft.com/sqlserver
> Thanks
> Michael
> "Mike C#" <xyz@.xyz.com> wrote in message
> news:%23RoXrrTHHHA.1816@.TK2MSFTNGP06.phx.gbl...
>

[SQL 2005] XQuery xs:NOTATION

Thanks
|||The first thing to test is, if the type is supported in XML Schema
collections... and it is not.
CREATE XML SCHEMA COLLECTION SCX AS
N'<xsd:schema targetNamespace="urn:example/customer"
xmlns:e="urn:example/customer"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<xsd:element name="buys" type="xsd:NOTATION"/>
</xsd:schema>'
returns
Msg 9337, Level 16, State 1, Line 1
The XML Schema type 'NOTATION' is not supported.
Since schema does not support the type, XQuery does not either.
If this type is important for your scenario, please file a bug report under
http://connect.microsoft.com/sqlserver
Thanks
Michael
"Mike C#" <xyz@.xyz.com> wrote in message
news:%23RoXrrTHHHA.1816@.TK2MSFTNGP06.phx.gbl...
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:7C916F7A-ED18-46E3-86F4-4E5B2E93D1A5@.microsoft.com...
> Hi John
> QN's don't have a constructor function per se, but there is an F&O
> function to create a QN. The QN casting is strictly QN to QN. The
> xs:NOTATION doesn't even work with the "instance of" operator (which was
> my test), and it comes back with the error message stating explicitly that
> no support for xs:NOTATION exists, so that's what I'm going with

Saturday, February 11, 2012

@terminate param for log shipping stored procs

SQL BOL says that the @.terminate parameter for sp_change_primary_role
defaults to 0 while it defaults to 1 in sp_change_secondary_role. In both
cases, this param "Specifies that all pending transactions be immediately
rolled back" and puts the db in single user mode while the stored proc runs.
I'm wondering why each of these has it different default value. I presume
that in both cases a value of 1 = true, meaning that it would do the
rollback. Am I correct in assuming this? In order to help me understand this
better, I hope someone could tell me why I would use the default values, and
in what cirucumstance I might not use the default values.archuleta37,
Your installation of the SQL Server 2000 Books Online needs to be updated.
There were documentation problems with these procedures. See:
http://support.microsoft.com/kb/291160 Terminate Default
http://support.microsoft.com/kb/298093 Job Id
These KBs also have a link to a corrected version of the BOL:
http://www.microsoft.com/downloads/release.asp?ReleaseID=31343
RLF
"archuleta37" <archuleta37@.discussions.microsoft.com> wrote in message
news:D0E72DDC-4147-4D25-AAE3-D83921D9A011@.microsoft.com...
> SQL BOL says that the @.terminate parameter for sp_change_primary_role
> defaults to 0 while it defaults to 1 in sp_change_secondary_role. In both
> cases, this param "Specifies that all pending transactions be immediately
> rolled back" and puts the db in single user mode while the stored proc
> runs.
> I'm wondering why each of these has it different default value. I presume
> that in both cases a value of 1 = true, meaning that it would do the
> rollback. Am I correct in assuming this? In order to help me understand
> this
> better, I hope someone could tell me why I would use the default values,
> and
> in what cirucumstance I might not use the default values.|||Thank you Russell,
This helps clarify a lot. I found that the link to the updated BOL you sent
is no longer valid, but I was easily able to search and find it at
http://www.microsoft.com/downloads/details.aspx?FamilyID=a6f79cb1-a420-445f-8a4b-bd77a7da194b&DisplayLang=en
The circumstance I'm testing assumes that the primary is completely
unavailable, yet when running sp_change_secondary_role there may be some
transaction log backups (.trn) files that are still loading. So I'm thinking
I should probably set the @.terminate param to 0. Would you agree with this
assessment or do you think I missing something in my reasoning?
"Russell Fields" wrote:
> archuleta37,
> Your installation of the SQL Server 2000 Books Online needs to be updated.
> There were documentation problems with these procedures. See:
> http://support.microsoft.com/kb/291160 Terminate Default
> http://support.microsoft.com/kb/298093 Job Id
> These KBs also have a link to a corrected version of the BOL:
> http://www.microsoft.com/downloads/release.asp?ReleaseID=31343
> RLF
> "archuleta37" <archuleta37@.discussions.microsoft.com> wrote in message
> news:D0E72DDC-4147-4D25-AAE3-D83921D9A011@.microsoft.com...
> > SQL BOL says that the @.terminate parameter for sp_change_primary_role
> > defaults to 0 while it defaults to 1 in sp_change_secondary_role. In both
> > cases, this param "Specifies that all pending transactions be immediately
> > rolled back" and puts the db in single user mode while the stored proc
> > runs.
> >
> > I'm wondering why each of these has it different default value. I presume
> > that in both cases a value of 1 = true, meaning that it would do the
> > rollback. Am I correct in assuming this? In order to help me understand
> > this
> > better, I hope someone could tell me why I would use the default values,
> > and
> > in what cirucumstance I might not use the default values.
>
>|||archuleta37,
I am afraid that I am not log shipping handy, so perhaps someone who does
this will have a quick answer. However, in the SQL Server 2000 Books Online
is a topic titled "How to set up and perform a log shipping role change
(Transact-SQL)" that seems to answer your question.
Also, a FAQ is found at: http://support.microsoft.com/kb/314515/en-us
RLF
"archuleta37" <archuleta37@.discussions.microsoft.com> wrote in message
news:509BEAF1-1B5D-4609-B92C-DF041A215B01@.microsoft.com...
> Thank you Russell,
> This helps clarify a lot. I found that the link to the updated BOL you
> sent
> is no longer valid, but I was easily able to search and find it at
> http://www.microsoft.com/downloads/details.aspx?FamilyID=a6f79cb1-a420-445f-8a4b-bd77a7da194b&DisplayLang=en
> The circumstance I'm testing assumes that the primary is completely
> unavailable, yet when running sp_change_secondary_role there may be some
> transaction log backups (.trn) files that are still loading. So I'm
> thinking
> I should probably set the @.terminate param to 0. Would you agree with this
> assessment or do you think I missing something in my reasoning?
>
> "Russell Fields" wrote:
>> archuleta37,
>> Your installation of the SQL Server 2000 Books Online needs to be
>> updated.
>> There were documentation problems with these procedures. See:
>> http://support.microsoft.com/kb/291160 Terminate Default
>> http://support.microsoft.com/kb/298093 Job Id
>> These KBs also have a link to a corrected version of the BOL:
>> http://www.microsoft.com/downloads/release.asp?ReleaseID=31343
>> RLF
>> "archuleta37" <archuleta37@.discussions.microsoft.com> wrote in message
>> news:D0E72DDC-4147-4D25-AAE3-D83921D9A011@.microsoft.com...
>> > SQL BOL says that the @.terminate parameter for sp_change_primary_role
>> > defaults to 0 while it defaults to 1 in sp_change_secondary_role. In
>> > both
>> > cases, this param "Specifies that all pending transactions be
>> > immediately
>> > rolled back" and puts the db in single user mode while the stored proc
>> > runs.
>> >
>> > I'm wondering why each of these has it different default value. I
>> > presume
>> > that in both cases a value of 1 = true, meaning that it would do the
>> > rollback. Am I correct in assuming this? In order to help me understand
>> > this
>> > better, I hope someone could tell me why I would use the default
>> > values,
>> > and
>> > in what cirucumstance I might not use the default values.
>>

@terminate param for log shipping stored procs

@NumericVal IS NOT NULL seems not to return a boolean.

I'm trying to ensure that only of the parameters is passed to my stored procedure.

BOL says that the IS [NOT] NULL operator (language construct?) will return a boolean. An IF statement takes an expression which results in a boolean so I was surprised to find that the below code doesn't parse.

CREATE PROC sp_OneParm(
@.NumericVal float = null,
@.StringVal nvarchar(200) = null,
@.DateVal datetime = null,
@.BitVal bit = null)
AS
DECLARE @.ValCount tinyint
SET @.ValCount = 0

-- Ensure we've only got one update value specified
IF @.NumericVal IS NOT NULL @.ValCount = @.ValCount + 1
IF @.StringVal IS NOT NULL @.ValCount = @.ValCount + 1
IF @.DateVal IS NOT NULL @.ValCount = @.ValCount + 1
IF @.BitVal IS NOT NULL @.ValCount = @.ValCount + 1
IF @.ValCount > 1 RAISERROR ('Only one @.*Val paramater may be specified when calling sp_OneParm()', 16, 1)

-- Other Stuff
GO

Am I missing something simple or do I need to restructure my code to achieve the logic I want?Sure :)

IF @.NumericVal IS NOT NULL SET @.ValCount = @.ValCount + 1|||Bugger. :o
Thank-you roac.

@@SERVERNAME returns NULL value... Can we adjust so that it returns the server name

We are running SQL 2000 in a non-clustered server. For some reason when we
select @.@.SERVERNAME we are getting a NULL value back. According to BOL ...
the information in returned by @.@.SERVERNAME may be different than the
SERVERNAME property of SERVERPROPERTY function. The SERVERNAME property
automatically reports changes in the network name of the computer. In
contrast, @.@.SERVERNAME does not report such changes. @.@.SERVERNAME reports
changes made to the local server name using the sp_addserver or
sp_dropserver stored procedure
Assuming that my server name is XYZ - I would assume that by executing the
following command we would be OK:
use master
go
sp_addserver 'XYZ', 'local'
go
But when executing this - we get the following message:
Server already exists.
Can someone advise the correct way to do this?
Thanks,
TomHi,
Try this
sp_dropserver 'XYZ'
go
sp_addserver 'XYZ', 'local'
go
After this stop and start the MS SQL Server service. Then login in Query
analyzer and execute SELECT @.@.SERVERNAME
Thanks
Hari
SQL Server MVP
"TJT" <TJT@.nospam.com> wrote in message
news:O9QwWELiFHA.1244@.TK2MSFTNGP14.phx.gbl...
> We are running SQL 2000 in a non-clustered server. For some reason when
> we
> select @.@.SERVERNAME we are getting a NULL value back. According to BOL
> ...
> the information in returned by @.@.SERVERNAME may be different than the
> SERVERNAME property of SERVERPROPERTY function. The SERVERNAME property
> automatically reports changes in the network name of the computer. In
> contrast, @.@.SERVERNAME does not report such changes. @.@.SERVERNAME reports
> changes made to the local server name using the sp_addserver or
> sp_dropserver stored procedure
> Assuming that my server name is XYZ - I would assume that by executing the
> following command we would be OK:
> use master
> go
> sp_addserver 'XYZ', 'local'
> go
> But when executing this - we get the following message:
> Server already exists.
> Can someone advise the correct way to do this?
> Thanks,
> Tom
>
>
>|||Hi Hari,
I have the same scenario as below, and I have even try to do two times
server restart also, but @.@.servername still returns Null to me, which is
different result from SERVERNAME property of SERVERPROPERTY function. Any
idea what else we can try? Thanks in advance!
Regards,
JC
"Hari Prasad" wrote:
> Hi,
> Try this
>
> sp_dropserver 'XYZ'
> go
> sp_addserver 'XYZ', 'local'
> go
> After this stop and start the MS SQL Server service. Then login in Query
> analyzer and execute SELECT @.@.SERVERNAME
> Thanks
> Hari
> SQL Server MVP
>
> "TJT" <TJT@.nospam.com> wrote in message
> news:O9QwWELiFHA.1244@.TK2MSFTNGP14.phx.gbl...
> > We are running SQL 2000 in a non-clustered server. For some reason when
> > we
> > select @.@.SERVERNAME we are getting a NULL value back. According to BOL
> > ...
> > the information in returned by @.@.SERVERNAME may be different than the
> > SERVERNAME property of SERVERPROPERTY function. The SERVERNAME property
> > automatically reports changes in the network name of the computer. In
> > contrast, @.@.SERVERNAME does not report such changes. @.@.SERVERNAME reports
> > changes made to the local server name using the sp_addserver or
> > sp_dropserver stored procedure
> >
> > Assuming that my server name is XYZ - I would assume that by executing the
> > following command we would be OK:
> >
> > use master
> > go
> >
> > sp_addserver 'XYZ', 'local'
> > go
> >
> > But when executing this - we get the following message:
> > Server already exists.
> >
> > Can someone advise the correct way to do this?
> >
> > Thanks,
> > Tom
> >
> >
> >
> >
> >
> >
>
>

Sunday, March 11, 2012

[SQL 2005] XQuery xs:NOTATION

[SQL 2005] XQuery xs:NOTATION

[SQL 2005] XQuery xs:NOTATION

[SQL 2005] XQuery xs:NOTATION

[SQL 2005] XQuery xs:NOTATION

Saturday, February 11, 2012

@terminate param for log shipping stored procs

@terminate param for log shipping stored procs

@terminate param for log shipping stored procs

@NumericVal IS NOT NULL seems not to return a boolean.

@@SERVERNAME returns NULL value... Can we adjust so that it returns the server name

@@SERVERNAME returns NULL value... Can we adjust so that it returns the server name

@@SERVERNAME returns NULL value... Can we adjust so that it returns the server name

sql rowcount

Blog Archive

About Me