Prev: Snapshot replication Problem
Next: drop replication
From: Himanshu on 8 Dec 2006 20:03
We detached a SQL 2000 database that was being replicated and attached it in
a SQL 2005 environment.

In the SQL 2005 environment (Server is already in production), the log is
filling up and not being truncated for obvious reasons. So I tried executing
the procedure sp_removeDBReplication but I get the following errors -

Msg 207, Level 16, State 1, Procedure sp_MSrepl_dropsubscription, Line 105
Invalid column name 'srvname'.

There is obviously a DDL change in the replication tables. Anyone know how
to get around this?

From: Sodi on 19 Dec 2006 15:27
I am getting the exact same situation where I have attached a SQL 2000
database to a SQL 2005 sp 1 environment. I am getting the same logging
symptons --- not being truncated, and the same error message when I run
sp_removeDBReplication.

If anyone has an answer, please reply!

"Himanshu" wrote:

> We detached a SQL 2000 database that was being replicated and attached it in
> a SQL 2005 environment.
>
> In the SQL 2005 environment (Server is already in production), the log is
> filling up and not being truncated for obvious reasons. So I tried executing
> the procedure sp_removeDBReplication but I get the following errors -
>
> Msg 207, Level 16, State 1, Procedure sp_MSrepl_dropsubscription, Line 105
> Invalid column name 'srvname'.
>
> There is obviously a DDL change in the replication tables. Anyone know how
> to get around this?
>
From: Himanshu on 19 Dec 2006 16:49
Hmm .. I was probably having a bad day :). It's actually pretty simple.

Just configure your new SQL 2005 box for replication, and then mark your
'problem' database as being replicated.

Then, in your problem database just run -
sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0, @time = 0,
@reset = 1

That'll remove the replication bit and release your secondary log truncation
marker.

Thanks.

"Himanshu" wrote:

> We detached a SQL 2000 database that was being replicated and attached it in
> a SQL 2005 environment.
>
> In the SQL 2005 environment (Server is already in production), the log is
> filling up and not being truncated for obvious reasons. So I tried executing
> the procedure sp_removeDBReplication but I get the following errors -
>
> Msg 207, Level 16, State 1, Procedure sp_MSrepl_dropsubscription, Line 105
> Invalid column name 'srvname'.
>
> There is obviously a DDL change in the replication tables. Anyone know how
> to get around this?
>
From: Sodi on 21 Dec 2006 15:40
Many thanks for the solution --- works like a charm!

My week's looking up now --- Happy Holidays!

"Himanshu" wrote:

> Hmm .. I was probably having a bad day :). It's actually pretty simple.
>
> Just configure your new SQL 2005 box for replication, and then mark your
> 'problem' database as being replicated.
>
> Then, in your problem database just run -
> sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0, @time = 0,
> @reset = 1
>
> That'll remove the replication bit and release your secondary log truncation
> marker.
>
> Thanks.
>
> "Himanshu" wrote:
>
> > We detached a SQL 2000 database that was being replicated and attached it in
> > a SQL 2005 environment.
> >
> > In the SQL 2005 environment (Server is already in production), the log is
> > filling up and not being truncated for obvious reasons. So I tried executing
> > the procedure sp_removeDBReplication but I get the following errors -
> >
> > Msg 207, Level 16, State 1, Procedure sp_MSrepl_dropsubscription, Line 105
> > Invalid column name 'srvname'.
> >
> > There is obviously a DDL change in the replication tables. Anyone know how
> > to get around this?
> >
 | 
Pages: 1
Prev: Snapshot replication Problem
Next: drop replication