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: Arithmetic overflow error converting numeric to data type numeric

Hello,
I'm using adonet to update the database hundreds of fields all at once and
got this exception/error:
"Arithmetic overflow error converting numeric to data type numeric", but it
doesn't tell me which specific column got overflown. Is there a way to find
out ? I have access to both the update code and the sql server.
Thank you very much in advance...Although I am not much of an ADO.Net person, I think that you get an errors
collection... SQL does return more info... Either it is in one of the other
messages or the one you are seeing is truncated... I did an arithmetic
overflow and got the following message..
Server: Msg 220, Level 16, State 2, Line 2
Arithmetic overflow error for data type tinyint, value = 3500.
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Zeng" <zzy@.nonospam.com> wrote in message
news:%23Whl0SBJEHA.2440@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I'm using adonet to update the database hundreds of fields all at once and
> got this exception/error:
> "Arithmetic overflow error converting numeric to data type numeric", but
it
> doesn't tell me which specific column got overflown. Is there a way to
find
> out ? I have access to both the update code and the sql server.
> Thank you very much in advance...
>|||hii
change the size of all your numeric fields in th data base to 38 and
precison to 0 and see..
ramesh|||If I don't error the error after that, how would I know which one?
"Ramesh" <ramesh@.mail.punecity.com> wrote in message
news:uJe8DkDKEHA.268@.TK2MSFTNGP11.phx.gbl...
> hii
> change the size of all your numeric fields in th data base to 38 and
> precison to 0 and see..
> ramesh
>sql

Error: Arithmetic overflow error converting numeric to data type numeric

Hello,
I'm using adonet to update the database hundreds of fields all at once and
got this exception/error:
"Arithmetic overflow error converting numeric to data type numeric", but it
doesn't tell me which specific column got overflown. Is there a way to find
out ? I have access to both the update code and the sql server.
Thank you very much in advance...Although I am not much of an ADO.Net person, I think that you get an errors
collection... SQL does return more info... Either it is in one of the other
messages or the one you are seeing is truncated... I did an arithmetic
overflow and got the following message..
Server: Msg 220, Level 16, State 2, Line 2
Arithmetic overflow error for data type tinyint, value = 3500.
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Zeng" <zzy@.nonospam.com> wrote in message
news:%23Whl0SBJEHA.2440@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I'm using adonet to update the database hundreds of fields all at once and
> got this exception/error:
> "Arithmetic overflow error converting numeric to data type numeric", but
it
> doesn't tell me which specific column got overflown. Is there a way to
find
> out ? I have access to both the update code and the sql server.
> Thank you very much in advance...
>|||hii
change the size of all your numeric fields in th data base to 38 and
precison to 0 and see..
ramesh|||If I don't error the error after that, how would I know which one?
"Ramesh" <ramesh@.mail.punecity.com> wrote in message
news:uJe8DkDKEHA.268@.TK2MSFTNGP11.phx.gbl...
> hii
> change the size of all your numeric fields in th data base to 38 and
> precison to 0 and see..
> ramesh
>

Error: Arithmetic overflow error converting numeric to data type numeric

Hello,
I'm using adonet to update the database hundreds of fields all at once and
got this exception/error:
"Arithmetic overflow error converting numeric to data type numeric", but it
doesn't tell me which specific column got overflown. Is there a way to find
out ? I have access to both the update code and the sql server.
Thank you very much in advance...
Although I am not much of an ADO.Net person, I think that you get an errors
collection... SQL does return more info... Either it is in one of the other
messages or the one you are seeing is truncated... I did an arithmetic
overflow and got the following message..
Server: Msg 220, Level 16, State 2, Line 2
Arithmetic overflow error for data type tinyint, value = 3500.
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Zeng" <zzy@.nonospam.com> wrote in message
news:%23Whl0SBJEHA.2440@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I'm using adonet to update the database hundreds of fields all at once and
> got this exception/error:
> "Arithmetic overflow error converting numeric to data type numeric", but
it
> doesn't tell me which specific column got overflown. Is there a way to
find
> out ? I have access to both the update code and the sql server.
> Thank you very much in advance...
>
|||hii
change the size of all your numeric fields in th data base to 38 and
precison to 0 and see..
ramesh
|||If I don't error the error after that, how would I know which one?
"Ramesh" <ramesh@.mail.punecity.com> wrote in message
news:uJe8DkDKEHA.268@.TK2MSFTNGP11.phx.gbl...
> hii
> change the size of all your numeric fields in th data base to 38 and
> precison to 0 and see..
> ramesh
>

Error: 701 Insufficient Memory - Nightly Data Update

We are running a relatively small data warehouse on a 2 CPU Dell server w/ 4
GB RAM running Win 2003 Server and SQL Server 2000 SP4. The only other load
on this server is IIS running our reporting application.
Our nightly data updates are a collection of relatively simple stored
procedures that extract data from DB2 on an AS/400 into the DW in a series o
f
stages. We're moving approximately 1 GB of data each night using the job
scheduler in SQL Server agent.
These nightly jobs fail at various steps with the following error:
"Executed as user: sa. There is insufficient system memory to run this
query. [SQLSTATE 42000] (Error 701) Could not create constraint. See
previous errors. [SQLSTATE 42000] (Error 1750) The statement has been
terminated. [SQLSTATE 01000] (Error 3621). The step failed."
I am eventually able to get each job to complete by restarting SQL Server
and SQL Server Agent after failure, and then restarting the jobs from the
last failed step. This is obviously an unacceptable solution.
I've read some of the other posts on similar problems, but none of the
solutions provided have been applicable to our problem.
This appears to be a memory leak. We have increased the memory available to
SQL Server as well as the virtual memory. These steps have simply delayed th
e
problem so that it occurs later in the process.
Can anyone provide any insights or guidance on how to address this problem?
--
Thanks, KenFirst hopefully you have enabled AWE, are running SQL Enterprise Ed. and
have applied the memory hotfix. But none of that would help directly with
error 1750 if it is the root cause.
Second hopefully, you don't have all your data files on the same disk on a
RAID 5 array. If you do, watch your CPUs when your loading. They will go
high and stay there if you are waiting on the disk. If you are waiting on
the disk, the DB2 connection could be trying to push when your system
doesn't have the resources.
some thoughts that might offer some leads.
d.
"Have Mercy" <HaveMercy@.discussions.microsoft.com> wrote in message
news:4369847C-CC04-4762-9B75-5A2D393F4241@.microsoft.com...
> We are running a relatively small data warehouse on a 2 CPU Dell server w/
4
> GB RAM running Win 2003 Server and SQL Server 2000 SP4. The only other
load
> on this server is IIS running our reporting application.
> Our nightly data updates are a collection of relatively simple stored
> procedures that extract data from DB2 on an AS/400 into the DW in a series
of
> stages. We're moving approximately 1 GB of data each night using the job
> scheduler in SQL Server agent.
> These nightly jobs fail at various steps with the following error:
> "Executed as user: sa. There is insufficient system memory to run this
> query. [SQLSTATE 42000] (Error 701) Could not create constraint. See
> previous errors. [SQLSTATE 42000] (Error 1750) The statement has been
> terminated. [SQLSTATE 01000] (Error 3621). The step failed."
> I am eventually able to get each job to complete by restarting SQL Server
> and SQL Server Agent after failure, and then restarting the jobs from the
> last failed step. This is obviously an unacceptable solution.
> I've read some of the other posts on similar problems, but none of the
> solutions provided have been applicable to our problem.
> This appears to be a memory leak. We have increased the memory available
to
> SQL Server as well as the virtual memory. These steps have simply delayed
the
> problem so that it occurs later in the process.
> Can anyone provide any insights or guidance on how to address this
problem?
> --
> Thanks, Ken|||Thanks D,
My problem is still not solved, but I thought I would give an update for
anyone else experiencing similar problems.
We are running SQL 2000 Enterprise Edition SP4; we have AWE enabled; data
files spread across the RAID array; and I did install the hotfix described i
n
the article: http://support.microsoft.com/kb/899761. In fact I installed a
cumulative hotfix that includes all hotfixes for SP4
(http://www.microsoft.com/downloads/...&displaylang=en).
I did discover that we had set 'Max degree of Parallelism' to 1, which means
we are only using 1 of the 2 processors available. It turns out that prior t
o
the 701 "Insufficient Memory" error, our jobs were failing with the error:
"The query processor could not start the necessary thread resources for
parallel query execution. [SQLSTATE 42000] (Error 8642)."
We circumvented this problem by using only 1 CPU. I would love to know if
anyone else has handled this error before. I can't find anything on Technet
or other SQL Server forums relating to this error.
I currently have a case opened with MSFT support. They have directed me to
disable AWE since it is not needed for only 4GB RAM. I've run several MSFT
analysis, profiling, and perf monitoring tools which have so far not
identified the root cause of the problem.
One thing I recently realized is that we are running Windows 2003 Standard
edition, which has more memory limitations than Enterprise edition. I'll be
researching this more tomorrow. Meanwhile, if any experts can shed light on
how this may relate to my problem. I would greatly appreciate your ideas.
--
Thanks, Ken
"d" wrote:

> First hopefully you have enabled AWE, are running SQL Enterprise Ed. and
> have applied the memory hotfix. But none of that would help directly with
> error 1750 if it is the root cause.
> Second hopefully, you don't have all your data files on the same disk on a
> RAID 5 array. If you do, watch your CPUs when your loading. They will go
> high and stay there if you are waiting on the disk. If you are waiting on
> the disk, the DB2 connection could be trying to push when your system
> doesn't have the resources.
> some thoughts that might offer some leads.
> d.
> "Have Mercy" <HaveMercy@.discussions.microsoft.com> wrote in message
> news:4369847C-CC04-4762-9B75-5A2D393F4241@.microsoft.com...
> 4
> load
> of
> to
> the
> problem?
>
>

Error: 701 Insufficient Memory - Nightly Data Update

We are running a relatively small data warehouse on a 2 CPU Dell server w/ 4
GB RAM running Win 2003 Server and SQL Server 2000 SP4. The only other load
on this server is IIS running our reporting application.
Our nightly data updates are a collection of relatively simple stored
procedures that extract data from DB2 on an AS/400 into the DW in a series of
stages. We're moving approximately 1 GB of data each night using the job
scheduler in SQL Server agent.
These nightly jobs fail at various steps with the following error:
"Executed as user: sa. There is insufficient system memory to run this
query. [SQLSTATE 42000] (Error 701) Could not create constraint. See
previous errors. [SQLSTATE 42000] (Error 1750) The statement has been
terminated. [SQLSTATE 01000] (Error 3621). The step failed."
I am eventually able to get each job to complete by restarting SQL Server
and SQL Server Agent after failure, and then restarting the jobs from the
last failed step. This is obviously an unacceptable solution.
I've read some of the other posts on similar problems, but none of the
solutions provided have been applicable to our problem.
This appears to be a memory leak. We have increased the memory available to
SQL Server as well as the virtual memory. These steps have simply delayed the
problem so that it occurs later in the process.
Can anyone provide any insights or guidance on how to address this problem?
--
Thanks, KenFirst hopefully you have enabled AWE, are running SQL Enterprise Ed. and
have applied the memory hotfix. But none of that would help directly with
error 1750 if it is the root cause.
Second hopefully, you don't have all your data files on the same disk on a
RAID 5 array. If you do, watch your CPUs when your loading. They will go
high and stay there if you are waiting on the disk. If you are waiting on
the disk, the DB2 connection could be trying to push when your system
doesn't have the resources.
some thoughts that might offer some leads.
d.
"Have Mercy" <HaveMercy@.discussions.microsoft.com> wrote in message
news:4369847C-CC04-4762-9B75-5A2D393F4241@.microsoft.com...
> We are running a relatively small data warehouse on a 2 CPU Dell server w/
4
> GB RAM running Win 2003 Server and SQL Server 2000 SP4. The only other
load
> on this server is IIS running our reporting application.
> Our nightly data updates are a collection of relatively simple stored
> procedures that extract data from DB2 on an AS/400 into the DW in a series
of
> stages. We're moving approximately 1 GB of data each night using the job
> scheduler in SQL Server agent.
> These nightly jobs fail at various steps with the following error:
> "Executed as user: sa. There is insufficient system memory to run this
> query. [SQLSTATE 42000] (Error 701) Could not create constraint. See
> previous errors. [SQLSTATE 42000] (Error 1750) The statement has been
> terminated. [SQLSTATE 01000] (Error 3621). The step failed."
> I am eventually able to get each job to complete by restarting SQL Server
> and SQL Server Agent after failure, and then restarting the jobs from the
> last failed step. This is obviously an unacceptable solution.
> I've read some of the other posts on similar problems, but none of the
> solutions provided have been applicable to our problem.
> This appears to be a memory leak. We have increased the memory available
to
> SQL Server as well as the virtual memory. These steps have simply delayed
the
> problem so that it occurs later in the process.
> Can anyone provide any insights or guidance on how to address this
problem?
> --
> Thanks, Ken|||Thanks D,
My problem is still not solved, but I thought I would give an update for
anyone else experiencing similar problems.
We are running SQL 2000 Enterprise Edition SP4; we have AWE enabled; data
files spread across the RAID array; and I did install the hotfix described in
the article: http://support.microsoft.com/kb/899761. In fact I installed a
cumulative hotfix that includes all hotfixes for SP4
(http://www.microsoft.com/downloads/details.aspx?familyid=4773BF7E-21AE-4F1E-AD48-6CA739E10217&displaylang=en).
I did discover that we had set 'Max Degree of Parallelism' to 1, which means
we are only using 1 of the 2 processors available. It turns out that prior to
the 701 "Insufficient Memory" error, our jobs were failing with the error:
"The query processor could not start the necessary thread resources for
parallel query execution. [SQLSTATE 42000] (Error 8642)."
We circumvented this problem by using only 1 CPU. I would love to know if
anyone else has handled this error before. I can't find anything on Technet
or other SQL Server forums relating to this error.
I currently have a case opened with MSFT support. They have directed me to
disable AWE since it is not needed for only 4GB RAM. I've run several MSFT
analysis, profiling, and perf monitoring tools which have so far not
identified the root cause of the problem.
One thing I recently realized is that we are running Windows 2003 Standard
edition, which has more memory limitations than Enterprise edition. I'll be
researching this more tomorrow. Meanwhile, if any experts can shed light on
how this may relate to my problem. I would greatly appreciate your ideas.
--
Thanks, Ken
"d" wrote:
> First hopefully you have enabled AWE, are running SQL Enterprise Ed. and
> have applied the memory hotfix. But none of that would help directly with
> error 1750 if it is the root cause.
> Second hopefully, you don't have all your data files on the same disk on a
> RAID 5 array. If you do, watch your CPUs when your loading. They will go
> high and stay there if you are waiting on the disk. If you are waiting on
> the disk, the DB2 connection could be trying to push when your system
> doesn't have the resources.
> some thoughts that might offer some leads.
> d.
> "Have Mercy" <HaveMercy@.discussions.microsoft.com> wrote in message
> news:4369847C-CC04-4762-9B75-5A2D393F4241@.microsoft.com...
> > We are running a relatively small data warehouse on a 2 CPU Dell server w/
> 4
> > GB RAM running Win 2003 Server and SQL Server 2000 SP4. The only other
> load
> > on this server is IIS running our reporting application.
> >
> > Our nightly data updates are a collection of relatively simple stored
> > procedures that extract data from DB2 on an AS/400 into the DW in a series
> of
> > stages. We're moving approximately 1 GB of data each night using the job
> > scheduler in SQL Server agent.
> >
> > These nightly jobs fail at various steps with the following error:
> >
> > "Executed as user: sa. There is insufficient system memory to run this
> > query. [SQLSTATE 42000] (Error 701) Could not create constraint. See
> > previous errors. [SQLSTATE 42000] (Error 1750) The statement has been
> > terminated. [SQLSTATE 01000] (Error 3621). The step failed."
> >
> > I am eventually able to get each job to complete by restarting SQL Server
> > and SQL Server Agent after failure, and then restarting the jobs from the
> > last failed step. This is obviously an unacceptable solution.
> >
> > I've read some of the other posts on similar problems, but none of the
> > solutions provided have been applicable to our problem.
> >
> > This appears to be a memory leak. We have increased the memory available
> to
> > SQL Server as well as the virtual memory. These steps have simply delayed
> the
> > problem so that it occurs later in the process.
> >
> > Can anyone provide any insights or guidance on how to address this
> problem?
> > --
> > Thanks, Ken
>
>sql

Error: 701 Insufficient Memory - Nightly Data Update

We are running a relatively small data warehouse on a 2 CPU Dell server w/ 4
GB RAM running Win 2003 Server and SQL Server 2000 SP4. The only other load
on this server is IIS running our reporting application.
Our nightly data updates are a collection of relatively simple stored
procedures that extract data from DB2 on an AS/400 into the DW in a series of
stages. We're moving approximately 1 GB of data each night using the job
scheduler in SQL Server agent.
These nightly jobs fail at various steps with the following error:
"Executed as user: sa. There is insufficient system memory to run this
query. [SQLSTATE 42000] (Error 701) Could not create constraint. See
previous errors. [SQLSTATE 42000] (Error 1750) The statement has been
terminated. [SQLSTATE 01000] (Error 3621). The step failed."
I am eventually able to get each job to complete by restarting SQL Server
and SQL Server Agent after failure, and then restarting the jobs from the
last failed step. This is obviously an unacceptable solution.
I've read some of the other posts on similar problems, but none of the
solutions provided have been applicable to our problem.
This appears to be a memory leak. We have increased the memory available to
SQL Server as well as the virtual memory. These steps have simply delayed the
problem so that it occurs later in the process.
Can anyone provide any insights or guidance on how to address this problem?
Thanks, Ken
First hopefully you have enabled AWE, are running SQL Enterprise Ed. and
have applied the memory hotfix. But none of that would help directly with
error 1750 if it is the root cause.
Second hopefully, you don't have all your data files on the same disk on a
RAID 5 array. If you do, watch your CPUs when your loading. They will go
high and stay there if you are waiting on the disk. If you are waiting on
the disk, the DB2 connection could be trying to push when your system
doesn't have the resources.
some thoughts that might offer some leads.
d.
"Have Mercy" <HaveMercy@.discussions.microsoft.com> wrote in message
news:4369847C-CC04-4762-9B75-5A2D393F4241@.microsoft.com...
> We are running a relatively small data warehouse on a 2 CPU Dell server w/
4
> GB RAM running Win 2003 Server and SQL Server 2000 SP4. The only other
load
> on this server is IIS running our reporting application.
> Our nightly data updates are a collection of relatively simple stored
> procedures that extract data from DB2 on an AS/400 into the DW in a series
of
> stages. We're moving approximately 1 GB of data each night using the job
> scheduler in SQL Server agent.
> These nightly jobs fail at various steps with the following error:
> "Executed as user: sa. There is insufficient system memory to run this
> query. [SQLSTATE 42000] (Error 701) Could not create constraint. See
> previous errors. [SQLSTATE 42000] (Error 1750) The statement has been
> terminated. [SQLSTATE 01000] (Error 3621). The step failed."
> I am eventually able to get each job to complete by restarting SQL Server
> and SQL Server Agent after failure, and then restarting the jobs from the
> last failed step. This is obviously an unacceptable solution.
> I've read some of the other posts on similar problems, but none of the
> solutions provided have been applicable to our problem.
> This appears to be a memory leak. We have increased the memory available
to
> SQL Server as well as the virtual memory. These steps have simply delayed
the
> problem so that it occurs later in the process.
> Can anyone provide any insights or guidance on how to address this
problem?
> --
> Thanks, Ken
|||Thanks D,
My problem is still not solved, but I thought I would give an update for
anyone else experiencing similar problems.
We are running SQL 2000 Enterprise Edition SP4; we have AWE enabled; data
files spread across the RAID array; and I did install the hotfix described in
the article: http://support.microsoft.com/kb/899761. In fact I installed a
cumulative hotfix that includes all hotfixes for SP4
(http://www.microsoft.com/downloads/d...displaylang=en).
I did discover that we had set 'Max Degree of Parallelism' to 1, which means
we are only using 1 of the 2 processors available. It turns out that prior to
the 701 "Insufficient Memory" error, our jobs were failing with the error:
"The query processor could not start the necessary thread resources for
parallel query execution. [SQLSTATE 42000] (Error 8642)."
We circumvented this problem by using only 1 CPU. I would love to know if
anyone else has handled this error before. I can't find anything on Technet
or other SQL Server forums relating to this error.
I currently have a case opened with MSFT support. They have directed me to
disable AWE since it is not needed for only 4GB RAM. I've run several MSFT
analysis, profiling, and perf monitoring tools which have so far not
identified the root cause of the problem.
One thing I recently realized is that we are running Windows 2003 Standard
edition, which has more memory limitations than Enterprise edition. I'll be
researching this more tomorrow. Meanwhile, if any experts can shed light on
how this may relate to my problem. I would greatly appreciate your ideas.
Thanks, Ken
"d" wrote:

> First hopefully you have enabled AWE, are running SQL Enterprise Ed. and
> have applied the memory hotfix. But none of that would help directly with
> error 1750 if it is the root cause.
> Second hopefully, you don't have all your data files on the same disk on a
> RAID 5 array. If you do, watch your CPUs when your loading. They will go
> high and stay there if you are waiting on the disk. If you are waiting on
> the disk, the DB2 connection could be trying to push when your system
> doesn't have the resources.
> some thoughts that might offer some leads.
> d.
> "Have Mercy" <HaveMercy@.discussions.microsoft.com> wrote in message
> news:4369847C-CC04-4762-9B75-5A2D393F4241@.microsoft.com...
> 4
> load
> of
> to
> the
> problem?
>
>

Error: 1203

Query:
update entries
set item_convert_status=0,
item_code=key_cross_ref.item_code,
mida=key_cross_ref.mida,
zeva_default=key_cross_ref.zeva_default
from entries,key_cross_ref
where entries.company_code=1
and (ltrim(rtrim(entries.origin_barcode))=key_cross_ref.barcode or
entries.origin_item_code=key_cross_ref.barcode)
Somtimes i get 2 error logs:
--Error: 1203, Severity: 20, State: 1
--Process ID 53 attempting to unlock unowned resource PAG: 30:1:136319..
Someone?I found this article http://support.microsoft.com/?kbid=814654
--
--
Jack Vamvas
___________________________________
Receive free SQL tips - www.ciquery.com/sqlserver.htm
___________________________________
"msforums.mircosoft.com" <chen_sh@.hotmail.com> wrote in message
news:ePdozacbGHA.2456@.TK2MSFTNGP04.phx.gbl...
> Query:
> update entries
> set item_convert_status=0,
> item_code=key_cross_ref.item_code,
> mida=key_cross_ref.mida,
> zeva_default=key_cross_ref.zeva_default
> from entries,key_cross_ref
> where entries.company_code=1
> and (ltrim(rtrim(entries.origin_barcode))=key_cross_ref.barcode or
> entries.origin_item_code=key_cross_ref.barcode)
> Somtimes i get 2 error logs:
> --Error: 1203, Severity: 20, State: 1
> --Process ID 53 attempting to unlock unowned resource PAG: 30:1:136319..
> Someone?
>

Error While Installing SQLServer CE

Hi,
I'm attempting to install SQL Server CE on a freshly built Windows XP (IIS 5.1).
I am an administrator on the machine.
I have run Windows Update on the Server, installed .NET Framework 1.1 SP1
and SQL Server 2000 with Service pack ...SP3a.
My Sql Server Registration lists the Product Version as 8.00.760.
I have attempted to install SQL Server CE using the setup.exe version
2.11.15.0 and sqlce20sql2ksp3a.exe version 2.11.15.0.
I have rebooted the machine.
I still get the error "SQL Server CE Server Tools is compatible only with
SQL Server 2000 Service Pack 1 or higher. etc..."
Does anyone have any ideas?
Thanks,
Sailu

Try running MSI (You can extract sqlce20sql2ksp3a.exe into a folder and get the MSI). This is a work around. But, one thing cleear is why Version Check by setup.exe fails.

Thanks,
Laxmi NRO MSFT, SQL Mobile, Microsoft Corporation