Invalid object name 'dbo.MSreplication_queue'.

I am attemption to update a record in a SQL 2005 table that is trans.
replicated with updates and I am receiving the following message...
Msg 208, Level 16, State 1, Procedure sp_MSsendtosqlqueue, Line 40
Invalid object name 'dbo.MSreplication_queue'.
Any ideas?
AHIA,
Larry...
Does the table dbo.MSreplication_queue exist in the subscribing database ?
In updatable scription scenerio, SQL Server fires ins/upd/del triggers which
will insert information into that table when a DML command is executed on the
replicated tables. So this table is one of the critical tables for the queue
replication to work.
I can think of only 2 reasons why you might be running into this error :
1. The table dbo.MSreplication_queue has been deleted. To see if the table
was dropped, take a look at the default trace report for the database "Schema
Changes Histroy" in the Management Studio.
or
2. The snapshot did not get applied to the subscriber successfully. Check
the distribution agents histroy to see if there has been any failures.
"LPR-3rd" wrote:

> I am attemption to update a record in a SQL 2005 table that is trans.
> replicated with updates and I am receiving the following message...
> Msg 208, Level 16, State 1, Procedure sp_MSsendtosqlqueue, Line 40
> Invalid object name 'dbo.MSreplication_queue'.
>
> Any ideas?
> AHIA,
> Larry...
>
|||What is the compatibility level of this database?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"LPR-3rd" <lreames@.gmail.com> wrote in message
news:1168541651.977581.286190@.i56g2000hsf.googlegr oups.com...
>I am attemption to update a record in a SQL 2005 table that is trans.
> replicated with updates and I am receiving the following message...
> Msg 208, Level 16, State 1, Procedure sp_MSsendtosqlqueue, Line 40
> Invalid object name 'dbo.MSreplication_queue'.
>
> Any ideas?
> AHIA,
> Larry...
>

invalid column error when updating a new column that was added by alter table

i am getting an error "Invalid Column name <column name>" message when runni
ng an update statement which updates a new column which was just added by an
alter table statement. If i run the alter statement and update statement se
perately, i don't get any e
rrors and it works. I only get this when they run together in a script or st
ored proc.
Is this a bug and what are the alternatives. Thanks.This is the way that the parser work. As the column doesn't (yet) exists at
parse time, the update will
generate the error. One way around it is to do the update with dynamic SQL.
OTOH, I'd re-consider why you have
to add a column dynamically in the first place (if possible).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"jsin" <anonymous@.discussions.microsoft.com> wrote in message
news:6A977D73-49D1-4229-92B1-B90B8E054540@.microsoft.com...
> i am getting an error "Invalid Column name <column name>" message when running an
update statement which
updates a new column which was just added by an alter table statement. If i
run the alter statement and update
statement seperately, i don't get any errors and it works. I only get this w
hen they run together in a script
or stored proc.
> Is this a bug and what are the alternatives. Thanks.

invalid column error when updating a new column that was added by alter table

i am getting an error "Invalid Column name <column name>" message when running an update statement which updates a new column which was just added by an alter table statement. If i run the alter statement and update statement seperately, i don't get any e
rrors and it works. I only get this when they run together in a script or stored proc.
Is this a bug and what are the alternatives. Thanks.
This is the way that the parser work. As the column doesn't (yet) exists at parse time, the update will
generate the error. One way around it is to do the update with dynamic SQL. OTOH, I'd re-consider why you have
to add a column dynamically in the first place (if possible).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"jsin" <anonymous@.discussions.microsoft.com> wrote in message
news:6A977D73-49D1-4229-92B1-B90B8E054540@.microsoft.com...
> i am getting an error "Invalid Column name <column name>" message when running an update statement which
updates a new column which was just added by an alter table statement. If i run the alter statement and update
statement seperately, i don't get any errors and it works. I only get this when they run together in a script
or stored proc.
> Is this a bug and what are the alternatives. Thanks.

Intra-query parallelism caused deadlock

Hi,
I am running a select query , which used left join on 5 tables. this is
reporting server there are no data updates, only select stmts. it has been
failing at runtime , the same query is running fine with different
parameters.
It is Dell machine with 4cpu/6gig /sql ent 2000/windows 2000 adv. max
degree of parallelism is 0 (before i change) , when i set max degree of
parallelism to 1 , then the query did run fine. As I remeber i havent
changed any configuration recently.
The query failed with following message.
Server: Msg 8650, Level 13, State 127, Line 1
Intra-query parallelism caused your server command (process ID #63) to
deadlock. Rerun the query without intra-query parallelism by using the query
hint option (maxdop 1).
Can somebody explain what caused it.
Thanks,
Subbu.
Hi!
Do please check the article at http://support.microsoft.com/?kbid=837983.
You will find possible reasons & workarounds there.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Subbaiahd" <subbaiahd@.hotmail.com> wrote in message
news:ewpo438gEHA.3264@.tk2msftngp13.phx.gbl...
> Hi,
> I am running a select query , which used left join on 5 tables. this is
> reporting server there are no data updates, only select stmts. it has been
> failing at runtime , the same query is running fine with different
> parameters.
> It is Dell machine with 4cpu/6gig /sql ent 2000/windows 2000 adv. max
> degree of parallelism is 0 (before i change) , when i set max degree of
> parallelism to 1 , then the query did run fine. As I remeber i havent
> changed any configuration recently.
>
> The query failed with following message.
> Server: Msg 8650, Level 13, State 127, Line 1
> Intra-query parallelism caused your server command (process ID #63) to
> deadlock. Rerun the query without intra-query parallelism by using the
query
> hint option (maxdop 1).
>
> Can somebody explain what caused it.
> Thanks,
> Subbu.
>
>
|||Thank you. I found it later.
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si > wrote in
message news:OUAafLChEHA.2916@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> Hi!
> Do please check the article at http://support.microsoft.com/?kbid=837983.
> You will find possible reasons & workarounds there.
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> Solid Quality Learning
> More than just Training
> www.SolidQualityLearning.com
> "Subbaiahd" <subbaiahd@.hotmail.com> wrote in message
> news:ewpo438gEHA.3264@.tk2msftngp13.phx.gbl...
been
> query
>

Intra-query parallelism caused deadlock

Hi,
I am running a select query , which used left join on 5 tables. this is
reporting server there are no data updates, only select stmts. it has been
failing at runtime , the same query is running fine with different
parameters.
It is Dell machine with 4cpu/6gig /sql ent 2000/windows 2000 adv. max
degree of parallelism is 0 (before i change) , when i set max degree of
parallelism to 1 , then the query did run fine. As I remeber i havent
changed any configuration recently.
The query failed with following message.
Server: Msg 8650, Level 13, State 127, Line 1
Intra-query parallelism caused your server command (process ID #63) to
deadlock. Rerun the query without intra-query parallelism by using the query
hint option (maxdop 1).
Can somebody explain what caused it.
Thanks,
Subbu.Hi!
Do please check the article at http://support.microsoft.com/?kbid=837983.
You will find possible reasons & workarounds there.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Subbaiahd" <subbaiahd@.hotmail.com> wrote in message
news:ewpo438gEHA.3264@.tk2msftngp13.phx.gbl...
> Hi,
> I am running a select query , which used left join on 5 tables. this is
> reporting server there are no data updates, only select stmts. it has been
> failing at runtime , the same query is running fine with different
> parameters.
> It is Dell machine with 4cpu/6gig /sql ent 2000/windows 2000 adv. max
> degree of parallelism is 0 (before i change) , when i set max degree of
> parallelism to 1 , then the query did run fine. As I remeber i havent
> changed any configuration recently.
>
> The query failed with following message.
> Server: Msg 8650, Level 13, State 127, Line 1
> Intra-query parallelism caused your server command (process ID #63) to
> deadlock. Rerun the query without intra-query parallelism by using the
query
> hint option (maxdop 1).
>
> Can somebody explain what caused it.
> Thanks,
> Subbu.
>
>|||Thank you. I found it later.
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in
message news:OUAafLChEHA.2916@.TK2MSFTNGP12.phx.gbl...
> Hi!
> Do please check the article at http://support.microsoft.com/?kbid=837983.
> You will find possible reasons & workarounds there.
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> Solid Quality Learning
> More than just Training
> www.SolidQualityLearning.com
> "Subbaiahd" <subbaiahd@.hotmail.com> wrote in message
> news:ewpo438gEHA.3264@.tk2msftngp13.phx.gbl...
been[vbcol=seagreen]
> query
>

Intra-query parallelism caused deadlock

Hi,
I am running a select query , which used left join on 5 tables. this is
reporting server there are no data updates, only select stmts. it has been
failing at runtime , the same query is running fine with different
parameters.
It is Dell machine with 4cpu/6gig /sql ent 2000/windows 2000 adv. max
degree of parallelism is 0 (before i change) , when i set max degree of
parallelism to 1 , then the query did run fine. As I remeber i havent
changed any configuration recently.
The query failed with following message.
Server: Msg 8650, Level 13, State 127, Line 1
Intra-query parallelism caused your server command (process ID #63) to
deadlock. Rerun the query without intra-query parallelism by using the query
hint option (maxdop 1).
Can somebody explain what caused it.
Thanks,
Subbu.Hi!
Do please check the article at http://support.microsoft.com/?kbid=837983.
You will find possible reasons & workarounds there.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Subbaiahd" <subbaiahd@.hotmail.com> wrote in message
news:ewpo438gEHA.3264@.tk2msftngp13.phx.gbl...
> Hi,
> I am running a select query , which used left join on 5 tables. this is
> reporting server there are no data updates, only select stmts. it has been
> failing at runtime , the same query is running fine with different
> parameters.
> It is Dell machine with 4cpu/6gig /sql ent 2000/windows 2000 adv. max
> degree of parallelism is 0 (before i change) , when i set max degree of
> parallelism to 1 , then the query did run fine. As I remeber i havent
> changed any configuration recently.
>
> The query failed with following message.
> Server: Msg 8650, Level 13, State 127, Line 1
> Intra-query parallelism caused your server command (process ID #63) to
> deadlock. Rerun the query without intra-query parallelism by using the
query
> hint option (maxdop 1).
>
> Can somebody explain what caused it.
> Thanks,
> Subbu.
>
>|||Thank you. I found it later.
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in
message news:OUAafLChEHA.2916@.TK2MSFTNGP12.phx.gbl...
> Hi!
> Do please check the article at http://support.microsoft.com/?kbid=837983.
> You will find possible reasons & workarounds there.
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> Solid Quality Learning
> More than just Training
> www.SolidQualityLearning.com
> "Subbaiahd" <subbaiahd@.hotmail.com> wrote in message
> news:ewpo438gEHA.3264@.tk2msftngp13.phx.gbl...
> > Hi,
> >
> > I am running a select query , which used left join on 5 tables. this is
> > reporting server there are no data updates, only select stmts. it has
been
> > failing at runtime , the same query is running fine with different
> > parameters.
> >
> > It is Dell machine with 4cpu/6gig /sql ent 2000/windows 2000 adv. max
> > degree of parallelism is 0 (before i change) , when i set max degree of
> > parallelism to 1 , then the query did run fine. As I remeber i havent
> > changed any configuration recently.
> >
> >
> >
> > The query failed with following message.
> >
> > Server: Msg 8650, Level 13, State 127, Line 1
> >
> > Intra-query parallelism caused your server command (process ID #63) to
> > deadlock. Rerun the query without intra-query parallelism by using the
> query
> > hint option (maxdop 1).
> >
> >
> >
> > Can somebody explain what caused it.
> >
> > Thanks,
> >
> > Subbu.
> >
> >
> >
> >
>