Showing posts with label version. Show all posts
Showing posts with label version. Show all posts

Wednesday, March 28, 2012

Incorrect syntax near XML-While creating XML Schema

Hi,

Im trying to create a xml schema like


CREATE XML SCHEMA COLLECTION BooksSchemaCollection AS
N'<?xml version="1.0" encoding="UTF-16"?>
<xsd:schema elementFormDefault="unqualified"
attributeFormDefault="unqualified"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" >
<xsd:element name="book">
<xsd:complexType mixed="false">
<xsd:sequence>
<xsd:element name="name" type="xsd:string"/>
<xsd:element name="author" type="xsd:string"/>
<xsd:element name="publisher" type="xsd:string"/>
<xsd:element name="cost" type="xsd:integer"/>
<xsd:element name="comments" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>';

But when i execute , im getting a error like Incorrect syntax near 'XML' .any one know why its comming??

Thanks

Hi ,

I use SqlServer 2005 and above SQL statement works fine on my pc.

Make sure you have correct permission.

To create an XML SCHEMA COLLECTION requires at least one of the following sets of permissions:

CONTROL permission on the server
ALTER ANY DATABASE permission on the server
ALTER permission on the database
CONTROL permission in the database
ALTER ANY SCHEMA permission and CREATE XML SCHEMA COLLECTION permission in the database
ALTER or CONTROL permission on the relational schema and CREATE XML SCHEMA COLLECTION permission in the database
sql

Wednesday, March 21, 2012

Incorrect Results -- is a hotfix available?

I have a query that is returning incorrect results. It is reproducible on
SQL 2000 SP4 (version 2040) and SP3a (version 760). It tried on 6 different
machines, all with different operating systems/hardware/etc.
Is there a hotfix available?
The following should not return any rows, but 1 row is returned:
declare @.fg table (FK1 int, FK2 int, FK3 int, FK4 int)
insert into @.fg
select 4, 4, 798, 13734
declare @.dg table (ID int, C1 varchar(20))
insert into @.dg
select 4, 'AAA'
declare @.drg table (C1 varchar(20))
insert into @.drg
select 'AAA'
declare @.fgt table (ID int, C1 char(1))
insert into @.fgt
select 4, 'F'
declare @.dwf table (ID int, FK1 int, FK2 int)
insert into @.dwf
select 798, 4, 46
declare @.f table (ID int)
insert into @.f
select 46
declare @.dwc table (ID int)
insert into @.dwc
select 4
select ID = 1
from @.fg fg
inner join @.dg dg on dg.ID = fg.FK1
inner join @.drg drg on drg.C1 = isnull(dg.C1, '')
inner join @.fgt fgt on fgt.ID = fg.FK2
inner join @.dwf dwf on dwf.ID = fg.FK3
inner join @.dwc dwc on dwc.ID = dwf.FK1
inner join @.f f on f.id = dwf.FK2
left join (select ID = 1, FK1 = 1234) ag on ag.ID = fg.FK4
left join (select ID = 1, C1 = '') dt on dt.ID = ag.FK1
inner join (select C1 = 1) c1 on c1.C1 = 1
inner join (select C2 = 1) c2 on c2.C2 = 1
where
isnull(dt.C1, '') = 'XYZ'This produces 0 rows on SQL Server 2005 (build 1399) and on SQL Server 2000
(build 2151 and build 2162).
You might want to see which (if any) specific hotfix references this issue.
See http://www.aspfaq.com/sql2000builds.asp
#2162 was available publicly until Friday or so, it was pulled due to a
couple of pretty serious issues. I noticed at least one of those issues on
#2151 also, which I am currently running, so please only try to obtain the
absolute highest build number you need, especially if you use a failover
cluster and/or rely on BULK INSERT.
Based on a quick scan, looks like the build # you need is 2145, but I did
not read the KB articles in full.
A
"davedave" <davedave@.discussions.microsoft.com> wrote in message
news:54BCCA28-6F9C-484D-976C-F357D2BF7D07@.microsoft.com...
>I have a query that is returning incorrect results. It is reproducible on
> SQL 2000 SP4 (version 2040) and SP3a (version 760). It tried on 6
> different
> machines, all with different operating systems/hardware/etc.
> Is there a hotfix available?
> The following should not return any rows, but 1 row is returned:
> declare @.fg table (FK1 int, FK2 int, FK3 int, FK4 int)
> insert into @.fg
> select 4, 4, 798, 13734
> declare @.dg table (ID int, C1 varchar(20))
> insert into @.dg
> select 4, 'AAA'
> declare @.drg table (C1 varchar(20))
> insert into @.drg
> select 'AAA'
> declare @.fgt table (ID int, C1 char(1))
> insert into @.fgt
> select 4, 'F'
> declare @.dwf table (ID int, FK1 int, FK2 int)
> insert into @.dwf
> select 798, 4, 46
> declare @.f table (ID int)
> insert into @.f
> select 46
> declare @.dwc table (ID int)
> insert into @.dwc
> select 4
> select ID = 1
> from @.fg fg
> inner join @.dg dg on dg.ID = fg.FK1
> inner join @.drg drg on drg.C1 = isnull(dg.C1, '')
> inner join @.fgt fgt on fgt.ID = fg.FK2
> inner join @.dwf dwf on dwf.ID = fg.FK3
> inner join @.dwc dwc on dwc.ID = dwf.FK1
> inner join @.f f on f.id = dwf.FK2
> left join (select ID = 1, FK1 = 1234) ag on ag.ID = fg.FK4
> left join (select ID = 1, C1 = '') dt on dt.ID = ag.FK1
> inner join (select C1 = 1) c1 on c1.C1 = 1
> inner join (select C2 = 1) c2 on c2.C2 = 1
> where
> isnull(dt.C1, '') = 'XYZ'
>

Wednesday, March 7, 2012

Incompability between MSSQL2000 SERVER 64 AND 32 BITS

eirs,
I'm using a "MSSQL2000 64 Bits" version, but I need to make some
distributed queries in the "MSSQL2000 32 bits" version. Do you know if there
is any incompatibility between these versions related to the using of the
linked server?
When I try to run a query from SQL 32 bits to 64 bits I have a sucess on
that execution, but when I try to execute query from 64 bits server I have
the message below:
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' reported an error.
[OLE/DB provider returned message: Unspecified error]
[OLE/DB provider returned message: The stored procedure required to complete
this operation could not be found on the server (they were supplied with the
ODBC setup disk for the SQL Server driver). Please contact your system
administrator.]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBSchemaRowset::GetRowset
returned 0x80004005:]
Linked Servers use xp .dll's. These are incompatible with the 64-bit OS.
When you call it on the 32-bit box, the .dll's run and the 64-bit responds
to the query.
The 64-bit BOL explains this.
Sincerely,
Anthony Thomas

"Wagner" <Wagner@.discussions.microsoft.com> wrote in message
news:102CA674-9EC2-4E53-ACEC-BB3A01EEC2F1@.microsoft.com...
eirs,
I'm using a "MSSQL2000 64 Bits" version, but I need to make some
distributed queries in the "MSSQL2000 32 bits" version. Do you know if
there
is any incompatibility between these versions related to the using of the
linked server?
When I try to run a query from SQL 32 bits to 64 bits I have a sucess on
that execution, but when I try to execute query from 64 bits server I have
the message below:
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' reported an error.
[OLE/DB provider returned message: Unspecified error]
[OLE/DB provider returned message: The stored procedure required to
complete
this operation could not be found on the server (they were supplied with
the
ODBC setup disk for the SQL Server driver). Please contact your system
administrator.]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBSchemaRowset::GetRowset
returned 0x80004005:]

Incompability between MSSQL2000 SERVER 64 AND 32 BITS

eirs,
I'm using a "MSSQL2000 64 Bits" version, but I need to make some
distributed queries in the "MSSQL2000 32 bits" version. Do you know if there
is any incompatibility between these versions related to the using of the
linked server?
When I try to run a query from SQL 32 bits to 64 bits I have a sucess on
that execution, but when I try to execute query from 64 bits server I have
the message below:
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' reported an error.
[OLE/DB provider returned message: Unspecified error]
[OLE/DB provider returned message: The stored procedure required to complete
this operation could not be found on the server (they were supplied with the
ODBC setup disk for the SQL Server driver). Please contact your system
administrator.]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBSchemaRowset::GetRowset
returned 0x80004005:]This is a multi-part message in MIME format.
--=_NextPart_000_042C_01C4E169.899D9C80
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
Linked Servers use xp .dll's. These are incompatible with the 64-bit OS.
When you call it on the 32-bit box, the .dll's run and the 64-bit responds
to the query.
The 64-bit BOL explains this.
Sincerely,
Anthony Thomas
"Wagner" <Wagner@.discussions.microsoft.com> wrote in message
news:102CA674-9EC2-4E53-ACEC-BB3A01EEC2F1@.microsoft.com...
eirs,
I'm using a "MSSQL2000 64 Bits" version, but I need to make some
distributed queries in the "MSSQL2000 32 bits" version. Do you know if
there
is any incompatibility between these versions related to the using of the
linked server?
When I try to run a query from SQL 32 bits to 64 bits I have a sucess on
that execution, but when I try to execute query from 64 bits server I have
the message below:
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' reported an error.
[OLE/DB provider returned message: Unspecified error]
[OLE/DB provider returned message: The stored procedure required to
complete
this operation could not be found on the server (they were supplied with
the
ODBC setup disk for the SQL Server driver). Please contact your system
administrator.]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBSchemaRowset::GetRowset
returned 0x80004005:]
--=_NextPart_000_042C_01C4E169.899D9C80
Content-Type: text/html;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

Linked Servers use xp .dll's. =These are incompatible with the 64-bit OS. When you call it on the 32-bit =box, the .dll's run and the 64-bit responds to the query.
The 64-bit BOL explains =this.
Sincerely,
Anthony Thomas
--
"Wagner" wrote in message news:102=CA674-9EC2-4E53-ACEC-BB3A01EEC2F1@.microsoft.com...eirs,I'm = using a "MSSQL2000 64 Bits" version, but I need to make some distributed queries in the "MSSQL2000 32 bits" version. Do you =know if there is any incompatibility between these versions related to the =using of the linked server?When I try to run a query from SQL 32 =bits to 64 bits I have a sucess on that execution, but when I try to execute =query from 64 bits server I have the message below:Server: Msg 7399, =Level 16, State 1, Line 1OLE DB provider 'SQLOLEDB' reported an =error. [OLE/DB provider returned message: Unspecified error][OLE/DB =provider returned message: The stored procedure required to complete this =operation could not be found on the server (they were supplied with the ODBC =setup disk for the SQL Server driver). Please contact your system administrator.]OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBSchemaRowset::GetRowset returned 0x80004005:]

--=_NextPart_000_042C_01C4E169.899D9C80--

Sunday, February 19, 2012

In Version 2005 : Dimension 'Time 1' : The source is not specified.

Hello,

I have the message 'Dimension 'Time 1' : The source is not specified.' when I processed or deploy my dimension 'Time 1'. This dimension has been create with the Assistant of the dimension.

I have the same problem with a cube !

What do I have to make?

Thanks

Looks like you missed something while designing your dimension. The error you are getting comes at validation stage. BI Dev Studio is trying to validate that all the objects in your database are defined correctly.

Try to run Dimension Wizard again and re-create the dimension.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.