Error: Contains more than the maximum number of prefixes. The max

I am running an update statement in query analyzer to update a database with
data from another database on another server.
I am running into the error : Error: Contains more than the maximum number
of prefixes. Maximum is 3
How do I overcome this error. I am the admin on both servers.http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=44062
DishanF
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||I was trying to do something similar by doing an update and "pushing" the da
ta across to a linked server with the following:
update ServerName.AAD.dbo.t_employee
set ServerName.AAD.dbo.t_employee.work_shift = wa.work_shift
from t_employee wa
where ServerName.AAD.dbo.t_employee.id = wa.id
and wa.id = '105'
I was also getting the following:
Server: Msg 117, Level 15, State 2, Line 4
The number name 'ServerName.AAD.dbo.t_employee' contains more than the maxim
um number of prefixes. The maximum is 3.
It's a simple, but not obvious, answer. Put the table you are updating in th
e FROM clause with an alias and update the alias, as follows:
update la
set la.work_shift = wa.work_shift
from ServerName.AAD.dbo.t_employee la, t_employee wa
where la.id = wa.id
and wa.id = '105'
You have to love simple answers. Finding them is the challenging part. :)sql

Error: Contains more than the maximum number of prefixes. Maximum

I am running an update statement in query analyzer to update a database with
data from another database on another server.
I am running into the error : Error: Contains more than the maximum number
of prefixes. Maximum is 3
How do I overcome this error. I am the admin on both servers.
> I am running an update statement in query analyzer to update a database
with
> data from another database on another server.
> I am running into the error : Error: Contains more than the maximum number
> of prefixes. Maximum is 3
> How do I overcome this error. I am the admin on both servers.
Object names in SQL Server have 4 parts: server.database.owner.objectname
Therefore, you ca have only 3 prefixes. Check the names in your Update
query.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com

Error: An invalid character was found in text content.

Hello All,
I am currently importing datarows into a sql 2000 database. when I use my
stored procedure which contains sp_xml_preparedocument... and FROM OPENXML,
I get the error stated above in the subject heading.
In reading other websites I have found that the error above:
An invalid character was found in text content.
You will get this error message if a character in the XML document does not
match the encoding attribute. Normally you will get this error message if
your XML document contains "foreign" characters, and the file was saved with
a single-byte encoding editor like Notepad, and no encoding attribute was
specified.
The actual error is:
Server: Msg 6603, Level 16, State 1, Procedure sp_xml_preparedocument, Line 15
XML parsing error: An Invalid character was found in text content.
Based on what I found on the other webisite, the only foreign character in
my data the è in ARKTX="XXX CRèME 1x20 KG".
Is there anyway to encode this character so I do not get a parsing error?
Thank you in advance
Eric
I found that I have to place an xml declaration
of
<?xml version="1.0" encoding="ISO-8859-1"?>
in my XML string so the sp_xml_prepared_Document stored procedure will treat
the data as UTF-8 and not the Database's code page.
"E-Cube" wrote:

> Hello All,
> I am currently importing datarows into a sql 2000 database. when I use my
> stored procedure which contains sp_xml_preparedocument... and FROM OPENXML,
> I get the error stated above in the subject heading.
> In reading other websites I have found that the error above:
> An invalid character was found in text content.
> You will get this error message if a character in the XML document does not
> match the encoding attribute. Normally you will get this error message if
> your XML document contains "foreign" characters, and the file was saved with
> a single-byte encoding editor like Notepad, and no encoding attribute was
> specified.
>
> The actual error is:
> Server: Msg 6603, Level 16, State 1, Procedure sp_xml_preparedocument, Line 15
> XML parsing error: An Invalid character was found in text content.
> Based on what I found on the other webisite, the only foreign character in
> my data the è in ARKTX="XXX CRèME 1x20 KG".
> Is there anyway to encode this character so I do not get a parsing error?
>
> Thank you in advance
> Eric
>

Error: An invalid character was found in text content.

Hello All,
I am currently importing datarows into a sql 2000 database. when I use my
stored procedure which contains sp_xml_preparedocument... and FROM OPENXML,
I get the error stated above in the subject heading.
In reading other websites I have found that the error above:
An invalid character was found in text content.
You will get this error message if a character in the XML document does not
match the encoding attribute. Normally you will get this error message if
your XML document contains "foreign" characters, and the file was saved with
a single-byte encoding editor like Notepad, and no encoding attribute was
specified.
The actual error is:
Server: Msg 6603, Level 16, State 1, Procedure sp_xml_preparedocument, Line
15
XML parsing error: An Invalid character was found in text content.
Based on what I found on the other webisite, the only foreign character in
my data the è in ARKTX="XXX CRèME 1x20 KG".
Is there anyway to encode this character so I do not get a parsing error?
Thank you in advance
EricI found that I have to place an xml declaration
of
<?xml version="1.0" encoding="ISO-8859-1"?>
in my XML string so the sp_xml_prepared_Document stored procedure will treat
the data as UTF-8 and not the Database's code page.
"E-Cube" wrote:

> Hello All,
> I am currently importing datarows into a sql 2000 database. when I use my
> stored procedure which contains sp_xml_preparedocument... and FROM OPENXML
,
> I get the error stated above in the subject heading.
> In reading other websites I have found that the error above:
> An invalid character was found in text content.
> You will get this error message if a character in the XML document does no
t
> match the encoding attribute. Normally you will get this error message if
> your XML document contains "foreign" characters, and the file was saved wi
th
> a single-byte encoding editor like Notepad, and no encoding attribute was
> specified.
>
> The actual error is:
> Server: Msg 6603, Level 16, State 1, Procedure sp_xml_preparedocument, Lin
e 15
> XML parsing error: An Invalid character was found in text content.
> Based on what I found on the other webisite, the only foreign character in
> my data the è in ARKTX="XXX CRèME 1x20 KG".
> Is there anyway to encode this character so I do not get a parsing error?
>
> Thank you in advance
> Eric
>sql

Error with Subscription

Hai, this is Srinivas Reddy. i have a problem in reporting services.

i have a parameter in one of my report, that parameter contains morethan 1300 rows. it is working fine with execution. but when i try to create a subscription, even the subscription page is not getting opened, instead i am getting an error "Error in XML document(1,10272)". I came to know that when this parameter contains less than 1213 rows (values), i am not getting this error and working fine with subscriptions.

I tried with another report which contains a parameter with 10 lakh rows queried against the same database , working fine with the subscription. so i came to know there is no limit for parameter values when it comes to subscriptions.

But, what might be the problem in my case?

If anybody knows this please help me.

Thanks in advance.

Can you post the corresponding error from the Report server logs - Reporting Services\Log Files\ReportingServices*.log

It could be caused by unprintable characters in the parameter's data.

Tudor Trufinescu

Error with default database collation

Hello
I am using SQL Server 2000 SP4
In my stored procedure I create table variable that contains one varchar
field and join that table variable with one of the database tables. I keep
getting error "Cannot resolve collation conflict for equal to operation.".
Both fields should have same collation. Table's field due to the fact that
it's collation is set to <database default> and <database default> is
Latin1_General_CI_AS. And according to Books online table variable also has
a
collation taken from <database default> if not explicitly set to other. So
what is the problem? If table variable field explicitly assign collation
Latin1_General_CI_AS - everything works fine. Why? My server's default
collation is Cyrillic_General_CI_AS. But how that can affect? I am not
allowed to use explicit collation in my SP.
Probably it is a known bug in SQL Server... Are then any fixes for that?
Thanks in advance.Seems like SQL2K doesn't pick up the current database for the connection whe
n you create a table
variable:
CREATE DATABASE x COLLATE Cyrillic_General_CI_AS
GO
USE x
CREATE TABLE t(c1 varchar(10))
INSERT INTO t VALUES('asd')
GO
--Error on 2000 sp3, fine on 2005
DECLARE @.t table(c1 varchar(10))
INSERT INTO @.t VALUES('asd')
SELECT * FROM t INNER JOIN @.t AS t2 ON t.c1 = t2.c1
GO
--Fine on both 2000 sp3 and 2005, as expected
DECLARE @.t table(c1 varchar(10) COLLATE database_Default)
INSERT INTO @.t VALUES('asd')
SELECT * FROM t INNER JOIN @.t AS t2 ON t.c1 = t2.c1
GO
--Error as expected on both 2000 sp3 and 2005
CREATE TABLE #t (c1 varchar(10))
INSERT INTO #t VALUES('asd')
SELECT * FROM t INNER JOIN #t AS t2 ON t.c1 = t2.c1
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Alexander Korol" <AlexanderKorol@.discussions.microsoft.com> wrote in messag
e
news:C5DD7198-4122-483E-BFD6-E83AF28002F7@.microsoft.com...
> Hello
> I am using SQL Server 2000 SP4
> In my stored procedure I create table variable that contains one varchar
> field and join that table variable with one of the database tables. I keep
> getting error "Cannot resolve collation conflict for equal to operation.".
> Both fields should have same collation. Table's field due to the fact that
> it's collation is set to <database default> and <database default> is
> Latin1_General_CI_AS. And according to Books online table variable also ha
s a
> collation taken from <database default> if not explicitly set to other. So
> what is the problem? If table variable field explicitly assign collation
> Latin1_General_CI_AS - everything works fine. Why? My server's default
> collation is Cyrillic_General_CI_AS. But how that can affect? I am not
> allowed to use explicit collation in my SP.
> Probably it is a known bug in SQL Server... Are then any fixes for that?
> Thanks in advance.

Error while using a slowly changing dimension transformation

I have a SSIS package which contains a number of slowly changing dimension transformations. While the majority work I have one which gives me the following error 'Error: The variable "System::LocaleID" is already on the read list. A variable may only be added once to either the read lock list or the write lock list. '. This error only occurs if the destination table holds data. If I truncate the table and reload the data then the package complete successful. The only difference I can see between this dimension transformation and the other dimension transforms is that the one in question has 2 business keys while the rest have 1.

Can anyone shed light on this?

Thanks

Have you installed SP1 and the hot fixes or SP2?

There was a bug in the variable handling which caused this error.
Although, the bug was not specifically for the SCD but variables in script task and derived columns and variables in general (so it would seem)|||

Yeah I've got SP2 installed.

Does this bug have a negative effect on the execution of the package? Has far has I can tell the package is completing. What is further confusing is if I empty the target dimension table I dont get the error. It only occurs on subsequent runs of the package when theres data present.

Error while using a slowly changing dimension transformation

I have a SSIS package which contains a number of slowly changing dimension transformations. While the majority work I have one which gives me the following error 'Error: The variable "System::LocaleID" is already on the read list. A variable may only be added once to either the read lock list or the write lock list. '. This error only occurs if the destination table holds data. If I truncate the table and reload the data then the package complete successful. The only difference I can see between this dimension transformation and the other dimension transforms is that the one in question has 2 business keys while the rest have 1.

Can anyone shed light on this?

Thanks

Have you installed SP1 and the hot fixes or SP2?

There was a bug in the variable handling which caused this error.
Although, the bug was not specifically for the SCD but variables in script task and derived columns and variables in general (so it would seem)|||

Yeah I've got SP2 installed.

Does this bug have a negative effect on the execution of the package? Has far has I can tell the package is completing. What is further confusing is if I empty the target dimension table I dont get the error. It only occurs on subsequent runs of the package when theres data present.

Error while exporting to Excel SP2

All of my reports work fine, while trying to export them to excel. But I'm
not able to render one Report to Excel. The Report contains some Lists and
the visibility depends on some(9) parameters. The rendering works fine with
all other Rendering-Formats. It seems that the Reporting Service (thread)
aborts and restart again. Is it possible that the Service quits because of
the Memory Limit (160 MB)? In the IIS I have created a seperate AppPool for
the Server and the Web-Service.
Because other services running on the Server, I put the memory limit for the
AppPool to 250 MB.
This is the Error while processing the Report via Report-Manager and/or
Web-Service:
Operation is not valid due to the current state of the object
rrRenderingError 400
Microsoft.ReportingServices.ReportRendering.ReportRenderingExceptionI had the same problem until I installed RS SP2 on my workstation
which is where I was actually receiving the error (Visual Studio 200
Report Designer, Layout view). Now it works great

Error while doing DTS from INFORMIX to MSSQL

Dear All,

I'm using the DTS to transfer data from Informix 7.30 UC9 to MS SQL 2000 Enterprise. The tables I'm transferring contains data for BaaN ERP.

While transferring certain tables, I am successful. On some, I get an error that says "Data overflow". It was caused by "DBTYPE_DBTIMESTAMP".

Any idea why this happens?

Thanks!I have seen it caused many of times in my experience with data conversion. It is generally caused when a date is incorrect.

BOL confirms Infomix information:
The Informix ODBC driver is not supported for use with DTS.
The Merant Informix OLE DB provider is supported for DTS imports from Informix, but not DTS exports to Informix. This driver also cannot be used to import meta data.

The Intersolv Informix ODBC driver is supported, but with the following restrictions:
BLOBs cannot be exported to Informix.

When creating new tables on Informix, the DTS Import/Export Wizard will incorrectly map the SQL Server 2000 datetime columns to the Informix 'Datetime year to fraction' data type. Manually change this to the Informix Date type.

The DTS meta data import will not import Informix catalog or table information.|||Thanks for such a speedy reply!

I've heard about this "Merant OLE driver" but I can't seem to download it from anywhere. Any clues?

Thanks again!

Originally posted by Satya
I have seen it caused many of times in my experience with data conversion. It is generally caused when a date is incorrect.

BOL confirms Infomix information:
The Informix ODBC driver is not supported for use with DTS.
The Merant Informix OLE DB provider is supported for DTS imports from Informix, but not DTS exports to Informix. This driver also cannot be used to import meta data.

The Intersolv Informix ODBC driver is supported, but with the following restrictions:
BLOBs cannot be exported to Informix.

When creating new tables on Informix, the DTS Import/Export Wizard will incorrectly map the SQL Server 2000 datetime columns to the Informix 'Datetime year to fraction' data type. Manually change this to the Informix Date type.

The DTS meta data import will not import Informix catalog or table information.