Replication triggers

Dear All,
the subscriber database contains no longer the (upd ,
ins , del) triggers of the replication.
How do i create them again , or do i need to drop the
subscription and do it all over again.
Please feedback urgently
Thanks in Advance
Dalia,
you should be able to script them out by creating a seaparate (fake)
subscription, and then apply them to the subscriber. I'd be a little
concerned that other details may be missing though and be tempted to
reinitialize. Also, I suspect that the excahnge type value is incorrect
which has caused this issue.
HTH,
Paul Ibison
|||I urge you to re-initialize your merge subscription(s), rerun your snapshot, and deploy it by rerunning your merge agent.
sql

Replication target table shrinks to zero

I want to replicate a database to a subscriber that will be used as a read
only copy. The data has to be replicated as close to instantly as possible.
To do this I set up a database export of objects and data to populate the
subscriber, then I set up transactional replication. To verify that
replication is working successfully, I count the rows in each table, there
are 3 tables in total. For one of the tables, the replication completes but
almost immediately afterward, the table starts to shrink, and after several
hours the record count is zero. This isn't happening to the other two
tables, and I can't figure out why.

If you have no idea what might be causing this, perhaps you can suggest
some places to start looking. This is Win2k SP4 with SQL 2000 SP3.

Thanks much."someguy" <nospam@.thanks.com> wrote in message
news:Xns945451BFDB728nospamthankscom@.207.35.177.13 5...
> I want to replicate a database to a subscriber that will be used as a read
> only copy. The data has to be replicated as close to instantly as
possible.
> To do this I set up a database export of objects and data to populate the
> subscriber, then I set up transactional replication. To verify that
> replication is working successfully, I count the rows in each table, there
> are 3 tables in total. For one of the tables, the replication completes
but
> almost immediately afterward, the table starts to shrink, and after
several
> hours the record count is zero. This isn't happening to the other two
> tables, and I can't figure out why.

Sounds like there's a trigger or another user operating on that table.

Replication itself should not cause a table to shrink (unless of course the
original source table is shrinking.)

> If you have no idea what might be causing this, perhaps you can suggest
> some places to start looking. This is Win2k SP4 with SQL 2000 SP3.
> Thanks much.

Replication Subscription Error

Hi,
I tried setting a server up as the publisher, distributor and subscriber.
When I tried to create either a push or pull subscription I got the following
message:
Error 14053: Cannot load the DLL replincrementlsn extended procedure, or one
of the DLLs it references. Reason: 126(error not found).
The subscription could not be updated at this time.
The subscription could not be created.
SQL Server Enterprise Manager could not create a pull subscription to
publication XXXX
Error 14053: Cannot load the DLL replincrementlsn extended procedure, or one
of the DLLs it references. Reason: 126(error not found).
The subscription could not be updated at this time.
The subscription could not be created.
Has anyone seen this before?
Server running SQL 2000 on Windows 2000 Server
Thanks
Something is not installed correctly. Reapply your latest service pack.
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
"DavidW" <DavidW@.discussions.microsoft.com> wrote in message
news:895B9996-9D97-4CAA-84F2-FF314F842E6F@.microsoft.com...
> Hi,
> I tried setting a server up as the publisher, distributor and subscriber.
> When I tried to create either a push or pull subscription I got the
> following
> message:
> Error 14053: Cannot load the DLL replincrementlsn extended procedure, or
> one
> of the DLLs it references. Reason: 126(error not found).
> The subscription could not be updated at this time.
> The subscription could not be created.
> SQL Server Enterprise Manager could not create a pull subscription to
> publication XXXX
> Error 14053: Cannot load the DLL replincrementlsn extended procedure, or
> one
> of the DLLs it references. Reason: 126(error not found).
> The subscription could not be updated at this time.
> The subscription could not be created.
> Has anyone seen this before?
> Server running SQL 2000 on Windows 2000 Server
> Thanks
>
|||Thank you Hilary, that has resolved the problem!
"Hilary Cotter" wrote:

> Something is not installed correctly. Reapply your latest service pack.
> --
> 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
> "DavidW" <DavidW@.discussions.microsoft.com> wrote in message
> news:895B9996-9D97-4CAA-84F2-FF314F842E6F@.microsoft.com...
>
>

Replication subscriber views, locks and blocks.

Quick question, do views on the subscription server create locking and
blocking issues?
I have 2 servers set-up with transactional replication. We have scheduled
reports running on the subscribing server, most of those reports using views.
The views seem to create performance, locking and blocking issues.
Thank you very much in advance.
Message posted via http://www.droptable.com
Yes they can. You might want to consider using indexed views depending on
your version and edition of SQL Server.
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
"Frank N via droptable.com" <u10790@.uwe> wrote in message
news:5a40019273826@.uwe...
> Quick question, do views on the subscription server create locking and
> blocking issues?
> I have 2 servers set-up with transactional replication. We have scheduled
> reports running on the subscribing server, most of those reports using
> views.
> The views seem to create performance, locking and blocking issues.
> Thank you very much in advance.
> --
> Message posted via http://www.droptable.com
|||A (non-dirty) read of data takes out a shared lock and this is not peculiar
to views. If these views are used for reporting purposes, you might want to
have a replica to be used for reporting eg using transactional replication,
or database mirroring with database snapshots.
Alternatively you could allow dirty reads (NOLOCK) on the tables in
question - depends on the business constraints.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||So if we place (nolock) hints on all the tables in all the views that should
eliminate the locking?
Paul Ibison wrote:
>A (non-dirty) read of data takes out a shared lock and this is not peculiar
>to views. If these views are used for reporting purposes, you might want to
>have a replica to be used for reporting eg using transactional replication,
>or database mirroring with database snapshots.
>Alternatively you could allow dirty reads (NOLOCK) on the tables in
>question - depends on the business constraints.
>Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
Message posted via http://www.droptable.com
|||Yes - or more easily set the transaction isolation-level to read
uncommitted.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Replication Stops at distributor in some cases

Hi,
I recently had a problem with a merge replication publication. In
some cases when data is changed on a subscriber, the change gets back
to the publisher but does not replicate from the publisher to the rest
of the subscribers. I checked the conflict viewer and there are no
conflicts. I am running SQL Server 2000 and I was wondering if anyone
is familiar with this problem.
Thanks,
Paul
Are you using any sort of filtering? This might account for this behavior.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Paul T." <weluvpaul@.hotmail.com> wrote in message
news:1fe3e09e.0408091019.79d49cf2@.posting.google.c om...
> Hi,
> I recently had a problem with a merge replication publication. In
> some cases when data is changed on a subscriber, the change gets back
> to the publisher but does not replicate from the publisher to the rest
> of the subscribers. I checked the conflict viewer and there are no
> conflicts. I am running SQL Server 2000 and I was wondering if anyone
> is familiar with this problem.
> Thanks,
> Paul
|||I do have some row filters on but none that comes into play in this
particular situation.
|||Can you give us some more details about this topology? How many subscribers,
etc.
I have tried to repro this on a local server with two subscribing database
and can't get the expected behavior. IE an update on Subscriber1 makes it to
the publisher and Susbcriber2. Same with updates on Susbcriber2.
Also can you query the conflict tables directly on the Publisher and
subcriber just to verify the conflict viewer is correct.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Paul T." <weluvpaul@.hotmail.com> wrote in message
news:1fe3e09e.0408120524.77f6d0ca@.posting.google.c om...
> I do have some row filters on but none that comes into play in this
> particular situation.
|||This publication has 12 subscribers (push subscriptions) that resync
every 2 hours. They are staggered to run 5 minutes apart. This only
happens with one particular table and I think it is perhaps a bug that
is just not listing the conflict. So far I have determined that this
happens when a personnel record is update on two different
subscribers. The only thing is in this case the fields being updated
on the two different subscribers do not overlap. So there should not
be any conflicts, and none of them are showing up in the conflict
manager. I also queried the conflict table and there were no rows in
there.
For example:
Field a and b are changed on subscriber X
Field d and c are changed on subscriber Y
publisher resyncs with X and gets the changes to field a and b
publisher resyncs with Y and gets changes to field d and c but does
update
Y with the changes from X.
I hope this helps, I am currently trying to reproduce this to have get
a more detailed version of what is going down. Thank you very much
for your help Hilary, it is appreciated.

replication setup help

Shailesh,
transactional replication over a VPN would be my choice,
with your home as a pull subscriber. If you haven't got
the VPN set up, then you can still use SQL Server logins
for synchronization and FTP for initialization.
This article should help in the configuration:
http://support.microsoft.com/?id=321822
Rgds,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Paul Ibison wrote:
> Shailesh,
> transactional replication over a VPN would be my choice,
> with your home as a pull subscriber. If you haven't got
> the VPN set up, then you can still use SQL Server logins
> for synchronization and FTP for initialization.
> This article should help in the configuration:
> http://support.microsoft.com/?id=321822
> Rgds,
> Paul Ibison
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
There are so many options and issues. I don't think there's any way
to avoid spending a week just to read through everything and
understand it all...
sql

replication scenario

Hi there,
I have two servers setup at two different locations, one a publisher(server
A) the other subscriber(server B). I'm using Merge replication and SQL server
2000.
We have teams working in remote areas gathering data in laptops that have
been setup as subscribers to server A.
How can i get the laptops to synchronise with server B incase server A fails?
Samman,
have a look in BOL for "merge replication, alternate synchronization
partners".
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Replication question - unable to modify table

I have disabled publisher, distributor and subscriber; no publications exist
on publisher. However, when I try to alter a table on former publisher I get
this error:
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot drop the
table 'dbo.MAIN' because it is being used for replication.
Please help, thank you in advance for your time!
Leon Shargorodsky
Run stored proc sp_removedbreplication and see if that fixes your problem.
Mike
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:37DFDC3E-7435-456E-A137-D94EDFED5915@.microsoft.com...
> I have disabled publisher, distributor and subscriber; no publications
exist
> on publisher. However, when I try to alter a table on former publisher I
get
> this error:
> ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot drop the
> table 'dbo.MAIN' because it is being used for replication.
> Please help, thank you in advance for your time!
> Leon Shargorodsky
|||No, I'm still getting the same error: "table is being used for replication"
"Mike Wengler" wrote:

> Run stored proc sp_removedbreplication and see if that fixes your problem.
> Mike
> "Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
> message news:37DFDC3E-7435-456E-A137-D94EDFED5915@.microsoft.com...
> exist
> get
>
>
|||NOT RECOMMENDED Under normal circumstances only after trying ALL other
solutions . . but I have had this problem resolved in the past by reseting
the value in replinfo column in sysobjects to 0.
HTH
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:8460093D-8C06-43AD-964B-06592F231ADE@.microsoft.com...
> No, I'm still getting the same error: "table is being used for
replication"[vbcol=seagreen]
> "Mike Wengler" wrote:
problem.[vbcol=seagreen]
in[vbcol=seagreen]
I[vbcol=seagreen]
the[vbcol=seagreen]
|||THANK YOU SO MUCH! It worked!!!
"Olu Adedeji" wrote:

> NOT RECOMMENDED Under normal circumstances only after trying ALL other
> solutions . . but I have had this problem resolved in the past by reseting
> the value in replinfo column in sysobjects to 0.
> HTH
>
>
> "Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
> message news:8460093D-8C06-43AD-964B-06592F231ADE@.microsoft.com...
> replication"
> problem.
> in
> I
> the
>
>

Replication question - unable to modify table

I have disabled publisher, distributor and subscriber; no publications exist
on publisher. However, when I try to alter a table on former publisher I get
this error:
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot drop the
table 'dbo.MAIN' because it is being used for replication.
Please help, thank you in advance for your time!
Leon ShargorodskyRun stored proc sp_removedbreplication and see if that fixes your problem.
Mike
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:37DFDC3E-7435-456E-A137-D94EDFED5915@.microsoft.com...
> I have disabled publisher, distributor and subscriber; no publications
exist
> on publisher. However, when I try to alter a table on former publisher I
get
> this error:
> ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot drop the
> table 'dbo.MAIN' because it is being used for replication.
> Please help, thank you in advance for your time!
> Leon Shargorodsky|||No, I'm still getting the same error: "table is being used for replication"
"Mike Wengler" wrote:
> Run stored proc sp_removedbreplication and see if that fixes your problem.
> Mike
> "Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
> message news:37DFDC3E-7435-456E-A137-D94EDFED5915@.microsoft.com...
> > I have disabled publisher, distributor and subscriber; no publications
> exist
> > on publisher. However, when I try to alter a table on former publisher I
> get
> > this error:
> >
> > ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot drop the
> > table 'dbo.MAIN' because it is being used for replication.
> >
> > Please help, thank you in advance for your time!
> >
> > Leon Shargorodsky
>
>|||NOT RECOMMENDED Under normal circumstances only after trying ALL other
solutions . . but I have had this problem resolved in the past by reseting
the value in replinfo column in sysobjects to 0.
HTH
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:8460093D-8C06-43AD-964B-06592F231ADE@.microsoft.com...
> No, I'm still getting the same error: "table is being used for
replication"
> "Mike Wengler" wrote:
> > Run stored proc sp_removedbreplication and see if that fixes your
problem.
> >
> > Mike
> >
> > "Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote
in
> > message news:37DFDC3E-7435-456E-A137-D94EDFED5915@.microsoft.com...
> > > I have disabled publisher, distributor and subscriber; no publications
> > exist
> > > on publisher. However, when I try to alter a table on former publisher
I
> > get
> > > this error:
> > >
> > > ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot drop
the
> > > table 'dbo.MAIN' because it is being used for replication.
> > >
> > > Please help, thank you in advance for your time!
> > >
> > > Leon Shargorodsky
> >
> >
> >|||THANK YOU SO MUCH! It worked!!!
"Olu Adedeji" wrote:
> NOT RECOMMENDED Under normal circumstances only after trying ALL other
> solutions . . but I have had this problem resolved in the past by reseting
> the value in replinfo column in sysobjects to 0.
> HTH
>
>
> "Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
> message news:8460093D-8C06-43AD-964B-06592F231ADE@.microsoft.com...
> > No, I'm still getting the same error: "table is being used for
> replication"
> >
> > "Mike Wengler" wrote:
> >
> > > Run stored proc sp_removedbreplication and see if that fixes your
> problem.
> > >
> > > Mike
> > >
> > > "Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote
> in
> > > message news:37DFDC3E-7435-456E-A137-D94EDFED5915@.microsoft.com...
> > > > I have disabled publisher, distributor and subscriber; no publications
> > > exist
> > > > on publisher. However, when I try to alter a table on former publisher
> I
> > > get
> > > > this error:
> > > >
> > > > ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot drop
> the
> > > > table 'dbo.MAIN' because it is being used for replication.
> > > >
> > > > Please help, thank you in advance for your time!
> > > >
> > > > Leon Shargorodsky
> > >
> > >
> > >
>
>

Replication question - unable to modify table

I have disabled publisher, distributor and subscriber; no publications exist
on publisher. However, when I try to alter a table on former publisher I get
this error:
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Canno
t drop the
table 'dbo.MAIN' because it is being used for replication.
Please help, thank you in advance for your time!
Leon ShargorodskyRun stored proc sp_removedbreplication and see if that fixes your problem.
Mike
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:37DFDC3E-7435-456E-A137-D94EDFED5915@.microsoft.com...
> I have disabled publisher, distributor and subscriber; no publications
exist
> on publisher. However, when I try to alter a table on former publisher I
get
> this error:
> ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Can
not drop the
> table 'dbo.MAIN' because it is being used for replication.
> Please help, thank you in advance for your time!
> Leon Shargorodsky|||No, I'm still getting the same error: "table is being used for replication"
"Mike Wengler" wrote:

> Run stored proc sp_removedbreplication and see if that fixes your problem.
> Mike
> "Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
> message news:37DFDC3E-7435-456E-A137-D94EDFED5915@.microsoft.com...
> exist
> get
>
>|||NOT RECOMMENDED Under normal circumstances only after trying ALL other
solutions . . but I have had this problem resolved in the past by reseting
the value in replinfo column in sysobjects to 0.
HTH
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:8460093D-8C06-43AD-964B-06592F231ADE@.microsoft.com...
> No, I'm still getting the same error: "table is being used for
replication"[vbcol=seagreen]
> "Mike Wengler" wrote:
>
problem.[vbcol=seagreen]
in[vbcol=seagreen]
I[vbcol=seagreen]
the[vbcol=seagreen]|||THANK YOU SO MUCH! It worked!!!
"Olu Adedeji" wrote:

> NOT RECOMMENDED Under normal circumstances only after trying ALL other
> solutions . . but I have had this problem resolved in the past by reseting
> the value in replinfo column in sysobjects to 0.
> HTH
>
>
> "Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
> message news:8460093D-8C06-43AD-964B-06592F231ADE@.microsoft.com...
> replication"
> problem.
> in
> I
> the
>
>

replication question

I have a transactional replication set up Between servers a as publisher and b as subscriber with tables aaa and bbb.
If i make a change on table aaa on the subscriber side should it over written by the value of the publication table value.

means

i have table aaa

id name date

1 bbbb 7/7/77

I have changed name as cccc on subscriber side, should it be over written to bbbb which is the value on publisher table.

Thanks.Transactional replication is a "one way street", from the publisher to the subscriber(s). You can enable RPC calls to funnel changes from the subscriber back to the publisher, but these aren't enabled by default. They are also a positive pain in the patoot to maintain!

Methinks thou desires Merge replication, bubba!

-PatP|||Thanks and I appreciate your response But, I was not asking whether the changes in the suscriber effects at publisher or not?If i made a change at subscriber like changing name from bbbb to cccc.So now the name at publisher database is bbbb and at subscriber is cccc.
Does the changed name at subscriber database(cccc) will be overwritten as bbbb which the name at publisher database. or it will be cccc at subscriber and bbbb at publisher.If it wont over write that name at subscriber how can we maintain same name at both the ends.
Thanks.|||Nothing will automagically force an update at the subscriber, but the next update to that row at the publisher will either a) update the name value at the subscriber, b) ignore the name value at the subscriber, or c) cause the replication distribution agent to fail. Which of the three will be determined by a combination of subscription and distributor settings.

-PatP

Replication question

Hi,
How do I know if any database is a publishing database or not?
Same way, how do I know if a particular server is a subscriber or not?
I want to know, the quickest and fastest way to get the publication name
and/or subscription name from the server.
regards
KP
Hi,
U can select for the Sysdatabases table in master database.
In that with the Category column value we can identified whether its
published or subscribe.
Values are
1 = Published.
2 = Subscribed.
4 = Merge Published.
8 = Merge Subscribed.
Herbert
"Krishnaprasad Paralikar" wrote:

> Hi,
> How do I know if any database is a publishing database or not?
> Same way, how do I know if a particular server is a subscriber or not?
> I want to know, the quickest and fastest way to get the publication name
> and/or subscription name from the server.
> regards
> KP
|||Check out DATABASEPROPERTYEX() in the BOL.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"Herbert" <Herbert@.discussions.microsoft.com> wrote in message
news:2C60C225-68EF-4670-99E4-8817CD2A80B4@.microsoft.com...
Hi,
U can select for the Sysdatabases table in master database.
In that with the Category column value we can identified whether its
published or subscribe.
Values are
1 = Published.
2 = Subscribed.
4 = Merge Published.
8 = Merge Subscribed.
Herbert
"Krishnaprasad Paralikar" wrote:

> Hi,
> How do I know if any database is a publishing database or not?
> Same way, how do I know if a particular server is a subscriber or not?
> I want to know, the quickest and fastest way to get the publication name
> and/or subscription name from the server.
> regards
> KP
sql

Replication Question

I set up a transactional push replication and basically
would like to use the subscriber as the archived
historical database server.
Once the snapshot is completed, I would like to delete
old records on the publisher article and not replicate
the deletion onto the archive database
server. How do you do this once the replication is set
between the publisher and subscriber?
TIA.
Thank you.
>--Original Message--
>On the article properties for the particular table(s)
you
>want to stop the deletes, on the commands tab write NONE
>for the propagation of delete commands.
>Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>.
>

replication question

Hi guys,
I have a question, not sure if it's do-able.
I have a transaction replication setup on Server A (Publisher) and Server B
is my Subscriber) I have over 100 tables in this publication.
I want to change order of columns to just one table in Publisher. is
there a way that I can do it without dropping publication?
let said my table have column A , column B, column C
I want to change order to Column B, Column C , Column A
nope. You would have to drop replication, script out your tables, export
your database, drop the tables, recreate them with the correct column order
and then reimport the data.
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
"Kevin" <pearl_77@.hotmail.com> wrote in message
news:O%23hiljsuFHA.3588@.tk2msftngp13.phx.gbl...
> Hi guys,
> I have a question, not sure if it's do-able.
> I have a transaction replication setup on Server A (Publisher) and Server
B
> is my Subscriber) I have over 100 tables in this publication.
> I want to change order of columns to just one table in Publisher. is
> there a way that I can do it without dropping publication?
>
> let said my table have column A , column B, column C
> I want to change order to Column B, Column C , Column A
>

Replication question

Hi,
How do I know if any database is a publishing database or not?
Same way, how do I know if a particular server is a subscriber or not?
I want to know, the quickest and fastest way to get the publication name
and/or subscription name from the server.
regards
KPHi,
U can select for the Sysdatabases table in master database.
In that with the Category column value we can identified whether its
published or subscribe.
Values are
1 = Published.
2 = Subscribed.
4 = Merge Published.
8 = Merge Subscribed.
Herbert
"Krishnaprasad Paralikar" wrote:

> Hi,
> How do I know if any database is a publishing database or not?
> Same way, how do I know if a particular server is a subscriber or not?
> I want to know, the quickest and fastest way to get the publication name
> and/or subscription name from the server.
> regards
> KP|||Check out DATABASEPROPERTYEX() in the BOL.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"Herbert" <Herbert@.discussions.microsoft.com> wrote in message
news:2C60C225-68EF-4670-99E4-8817CD2A80B4@.microsoft.com...
Hi,
U can select for the Sysdatabases table in master database.
In that with the Category column value we can identified whether its
published or subscribe.
Values are
1 = Published.
2 = Subscribed.
4 = Merge Published.
8 = Merge Subscribed.
Herbert
"Krishnaprasad Paralikar" wrote:

> Hi,
> How do I know if any database is a publishing database or not?
> Same way, how do I know if a particular server is a subscriber or not?
> I want to know, the quickest and fastest way to get the publication name
> and/or subscription name from the server.
> regards
> KP

Replication question

Hi,
How do I know if any database is a publishing database or not?
Same way, how do I know if a particular server is a subscriber or not?
I want to know, the quickest and fastest way to get the publication name
and/or subscription name from the server.
regards
KPHi,
U can select for the Sysdatabases table in master database.
In that with the Category column value we can identified whether its
published or subscribe.
Values are
1 = Published.
2 = Subscribed.
4 = Merge Published.
8 = Merge Subscribed.
--
Herbert
"Krishnaprasad Paralikar" wrote:
> Hi,
> How do I know if any database is a publishing database or not?
> Same way, how do I know if a particular server is a subscriber or not?
> I want to know, the quickest and fastest way to get the publication name
> and/or subscription name from the server.
> regards
> KP|||Check out DATABASEPROPERTYEX() in the BOL.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"Herbert" <Herbert@.discussions.microsoft.com> wrote in message
news:2C60C225-68EF-4670-99E4-8817CD2A80B4@.microsoft.com...
Hi,
U can select for the Sysdatabases table in master database.
In that with the Category column value we can identified whether its
published or subscribe.
Values are
1 = Published.
2 = Subscribed.
4 = Merge Published.
8 = Merge Subscribed.
--
Herbert
"Krishnaprasad Paralikar" wrote:
> Hi,
> How do I know if any database is a publishing database or not?
> Same way, how do I know if a particular server is a subscriber or not?
> I want to know, the quickest and fastest way to get the publication name
> and/or subscription name from the server.
> regards
> KP

Replication Problems from Subscriber to Publisher.

Hi,
I am experiencing some difficulties with DataBase Replication. I have
two SQL 2000 servers running on different machines (The server is
running on Windows 2000 Server, and the other on Window 2000
Professional).
I have created a database with one table. Have then Published this
database, and setup a Subscription. (The Publication is Transactional,
using Immediate updating.)
If I amend/insert/delete any rows/columns at the Publisher, the
changes are immediately propagated to the Subscriber. The problem I'm
having is when the Subscriber makes any changes to the Table, SQL
generates the following error:
Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Server]Could
not execute procedure 'sp_MSsync_upd_<tablename>_1' on remote server
'SQLOLEDB'.
I have used the Profiler, and determined that the table change
executes the trigger 'trg_MSsync_upd_<tablename>'. This trigger is
then failing when it try's to execute the following statement:
exec @.retcode = OpenDataSource('SQLOLEDB',N'SERVER=SQLServer;UID=s a;PWD=;').[<databasename>].[dbo].[sp_MSsync_del_<tablename>_1]'
...
And since I didn't want to re-code the triggers automatically created
by SQL, I'm trying to figure out why the execution of the Remote
Stored
Procedure doesn't work.
Any help is much appreciated.
Thanks in Advance.
Rick 8-)
Two things to check. First, make sure the distributor and/or the publisher
servers have allowed remote proc execution through sp_configure.
Next, make sure your Win 2K Pro installation is running the SQL Server
service accounts under an id that has access to the distributor/publisher or
has the correct sign-in information.
Sincerely,
Anthony Thomas
"Rick Knight" wrote:

> Hi,
> I am experiencing some difficulties with DataBase Replication. I have
> two SQL 2000 servers running on different machines (The server is
> running on Windows 2000 Server, and the other on Window 2000
> Professional).
> I have created a database with one table. Have then Published this
> database, and setup a Subscription. (The Publication is Transactional,
> using Immediate updating.)
> If I amend/insert/delete any rows/columns at the Publisher, the
> changes are immediately propagated to the Subscriber. The problem I'm
> having is when the Subscriber makes any changes to the Table, SQL
> generates the following error:
> Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Server]Could
> not execute procedure 'sp_MSsync_upd_<tablename>_1' on remote server
> 'SQLOLEDB'.
> I have used the Profiler, and determined that the table change
> executes the trigger 'trg_MSsync_upd_<tablename>'. This trigger is
> then failing when it try's to execute the following statement:
> exec @.retcode = OpenDataSource('SQLOLEDB',N'SERVER=SQLServer;UID=s a;PWD=;').[<databasename>].[dbo].[sp_MSsync_del_<tablename>_1]'
> ...
> And since I didn't want to re-code the triggers automatically created
> by SQL, I'm trying to figure out why the execution of the Remote
> Stored
> Procedure doesn't work.
> Any help is much appreciated.
> Thanks in Advance.
> Rick 8-)
>
|||Thanks for the feedback Anthony, But I have check both of these, and
still no luck. Now however the error message is different.
Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB
error trace [OLE/DB Provider 'SQLOLEDB' IUnknow QueryInterface
returned 0x80070005: Access denied.
BTW: Replication from the Publisher to the Subscriber still works okay
though.
Have you any other suggestions?
Thanks in Advance
Rick
"AnthonyThomas" <AnthonyThomas@.discussions.microsoft.com> wrote in message news:<4DCC547D-F875-4F14-8B65-F02CD34B8088@.microsoft.com>...[vbcol=seagreen]
> Two things to check. First, make sure the distributor and/or the publisher
> servers have allowed remote proc execution through sp_configure.
> Next, make sure your Win 2K Pro installation is running the SQL Server
> service accounts under an id that has access to the distributor/publisher or
> has the correct sign-in information.
> Sincerely,
>
> Anthony Thomas
>
> "Rick Knight" wrote:
|||That error message means you've granted the publisher/distributer SQL Agent
account access to the subscriber machine but that the reverse is not true.
In order to do a Pull, the subscriber must have login rights to the
distributer/publisher server.
Sincerely,
Anthony Thomas
"Rick Knight" wrote:

> Thanks for the feedback Anthony, But I have check both of these, and
> still no luck. Now however the error message is different.
> Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB
> error trace [OLE/DB Provider 'SQLOLEDB' IUnknow QueryInterface
> returned 0x80070005: Access denied.
> BTW: Replication from the Publisher to the Subscriber still works okay
> though.
> Have you any other suggestions?
> Thanks in Advance
> Rick
>
> "AnthonyThomas" <AnthonyThomas@.discussions.microsoft.com> wrote in message news:<4DCC547D-F875-4F14-8B65-F02CD34B8088@.microsoft.com>...
>
sql

Replication Problems from Subscriber to Publisher.

Hi,
I am experiencing some difficulties with DataBase Replication. I have
two SQL 2000 servers running on different machines (The server is
running on Windows 2000 Server, and the other on Window 2000
Professional).
I have created a database with one table. Have then Published this
database, and setup a Subscription. (The Publication is Transactional,
using Immediate updating.)
If I amend/insert/delete any rows/columns at the Publisher, the
changes are immediately propagated to the Subscriber. The problem I'm
having is when the Subscriber makes any changes to the Table, SQL
generates the following error:
Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Server]
Could
not execute procedure 'sp_MSsync_upd_<tablename>_1' on remote server
'SQLOLEDB'.
I have used the Profiler, and determined that the table change
executes the trigger 'trg_MSsync_upd_<tablename>'. This trigger is
then failing when it try's to execute the following statement:
exec @.retcode = OpenDataSource('SQLOLEDB',N'SERVER=SQLSe
rver;UID=sa;PWD=;').
[<databasename>].[dbo].[sp_MSsync_del_<tablename>_1]'
...
And since I didn't want to re-code the triggers automatically created
by SQL, I'm trying to figure out why the execution of the Remote
Stored
Procedure doesn't work.
Any help is much appreciated.
Thanks in Advance.
Rick 8-)Two things to check. First, make sure the distributor and/or the publisher
servers have allowed remote proc execution through sp_configure.
Next, make sure your Win 2K Pro installation is running the SQL Server
service accounts under an id that has access to the distributor/publisher or
has the correct sign-in information.
Sincerely,
Anthony Thomas
"Rick Knight" wrote:

> Hi,
> I am experiencing some difficulties with DataBase Replication. I have
> two SQL 2000 servers running on different machines (The server is
> running on Windows 2000 Server, and the other on Window 2000
> Professional).
> I have created a database with one table. Have then Published this
> database, and setup a Subscription. (The Publication is Transactional,
> using Immediate updating.)
> If I amend/insert/delete any rows/columns at the Publisher, the
> changes are immediately propagated to the Subscriber. The problem I'm
> having is when the Subscriber makes any changes to the Table, SQL
> generates the following error:
> Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Serve
r]Could
> not execute procedure 'sp_MSsync_upd_<tablename>_1' on remote server
> 'SQLOLEDB'.
> I have used the Profiler, and determined that the table change
> executes the trigger 'trg_MSsync_upd_<tablename>'. This trigger is
> then failing when it try's to execute the following statement:
> exec @.retcode = OpenDataSource('SQLOLEDB',N'SERVER=SQLSe
rver;UID=sa;PWD=;'
).[<databasename>].[dbo].[sp_MSsync_del_<tablename>_1]'
> ...
> And since I didn't want to re-code the triggers automatically created
> by SQL, I'm trying to figure out why the execution of the Remote
> Stored
> Procedure doesn't work.
> Any help is much appreciated.
> Thanks in Advance.
> Rick 8-)
>|||Thanks for the feedback Anthony, But I have check both of these, and
still no luck. Now however the error message is different.
Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Server]
OLE DB
error trace [OLE/DB Provider 'SQLOLEDB' IUnknow QueryInterface
returned 0x80070005: Access denied.
BTW: Replication from the Publisher to the Subscriber still works okay
though.
Have you any other suggestions?
Thanks in Advance
Rick
"AnthonyThomas" <AnthonyThomas@.discussions.microsoft.com> wrote in message news:<4DCC547D-F8
75-4F14-8B65-F02CD34B8088@.microsoft.com>...[vbcol=seagreen]
> Two things to check. First, make sure the distributor and/or the publishe
r
> servers have allowed remote proc execution through sp_configure.
> Next, make sure your Win 2K Pro installation is running the SQL Server
> service accounts under an id that has access to the distributor/publisher
or
> has the correct sign-in information.
> Sincerely,
>
> Anthony Thomas
>
> "Rick Knight" wrote:
>|||That error message means you've granted the publisher/distributer SQL Agent
account access to the subscriber machine but that the reverse is not true.
In order to do a Pull, the subscriber must have login rights to the
distributer/publisher server.
Sincerely,
Anthony Thomas
"Rick Knight" wrote:

> Thanks for the feedback Anthony, But I have check both of these, and
> still no luck. Now however the error message is different.
> Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Serve
r]OLE DB
> error trace [OLE/DB Provider 'SQLOLEDB' IUnknow QueryInterface
> returned 0x80070005: Access denied.
> BTW: Replication from the Publisher to the Subscriber still works okay
> though.
> Have you any other suggestions?
> Thanks in Advance
> Rick
>
> "AnthonyThomas" <AnthonyThomas@.discussions.microsoft.com> wrote in message
news:<4DCC547D-F875-4F14-8B65-F02CD34B8088@.microsoft.com>...
>

Replication Problems from Subscriber to Publisher.

Hi,
I am experiencing some difficulties with DataBase Replication. I have
two SQL 2000 servers running on different machines (The server is
running on Windows 2000 Server, and the other on Window 2000
Professional).
I have created a database with one table. Have then Published this
database, and setup a Subscription. (The Publication is Transactional,
using Immediate updating.)
If I amend/insert/delete any rows/columns at the Publisher, the
changes are immediately propagated to the Subscriber. The problem I'm
having is when the Subscriber makes any changes to the Table, SQL
generates the following error:
Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Server]Could
not execute procedure 'sp_MSsync_upd_<tablename>_1' on remote server
'SQLOLEDB'.
I have used the Profiler, and determined that the table change
executes the trigger 'trg_MSsync_upd_<tablename>'. This trigger is
then failing when it try's to execute the following statement:
exec @.retcode = OpenDataSource('SQLOLEDB',N'SERVER=SQLServer;UID=sa;PWD=;').[<databasename>].[dbo].[sp_MSsync_del_<tablename>_1]'
...
And since I didn't want to re-code the triggers automatically created
by SQL, I'm trying to figure out why the execution of the Remote
Stored
Procedure doesn't work.
Any help is much appreciated.
Thanks in Advance.
Rick 8-)Two things to check. First, make sure the distributor and/or the publisher
servers have allowed remote proc execution through sp_configure.
Next, make sure your Win 2K Pro installation is running the SQL Server
service accounts under an id that has access to the distributor/publisher or
has the correct sign-in information.
Sincerely,
Anthony Thomas
"Rick Knight" wrote:
> Hi,
> I am experiencing some difficulties with DataBase Replication. I have
> two SQL 2000 servers running on different machines (The server is
> running on Windows 2000 Server, and the other on Window 2000
> Professional).
> I have created a database with one table. Have then Published this
> database, and setup a Subscription. (The Publication is Transactional,
> using Immediate updating.)
> If I amend/insert/delete any rows/columns at the Publisher, the
> changes are immediately propagated to the Subscriber. The problem I'm
> having is when the Subscriber makes any changes to the Table, SQL
> generates the following error:
> Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Server]Could
> not execute procedure 'sp_MSsync_upd_<tablename>_1' on remote server
> 'SQLOLEDB'.
> I have used the Profiler, and determined that the table change
> executes the trigger 'trg_MSsync_upd_<tablename>'. This trigger is
> then failing when it try's to execute the following statement:
> exec @.retcode = OpenDataSource('SQLOLEDB',N'SERVER=SQLServer;UID=sa;PWD=;').[<databasename>].[dbo].[sp_MSsync_del_<tablename>_1]'
> ...
> And since I didn't want to re-code the triggers automatically created
> by SQL, I'm trying to figure out why the execution of the Remote
> Stored
> Procedure doesn't work.
> Any help is much appreciated.
> Thanks in Advance.
> Rick 8-)
>|||Thanks for the feedback Anthony, But I have check both of these, and
still no luck. Now however the error message is different.
Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB
error trace [OLE/DB Provider 'SQLOLEDB' IUnknow QueryInterface
returned 0x80070005: Access denied.
BTW: Replication from the Publisher to the Subscriber still works okay
though.
Have you any other suggestions?
Thanks in Advance
Rick :)
"AnthonyThomas" <AnthonyThomas@.discussions.microsoft.com> wrote in message news:<4DCC547D-F875-4F14-8B65-F02CD34B8088@.microsoft.com>...
> Two things to check. First, make sure the distributor and/or the publisher
> servers have allowed remote proc execution through sp_configure.
> Next, make sure your Win 2K Pro installation is running the SQL Server
> service accounts under an id that has access to the distributor/publisher or
> has the correct sign-in information.
> Sincerely,
>
> Anthony Thomas
>
> "Rick Knight" wrote:
> > Hi,
> >
> > I am experiencing some difficulties with DataBase Replication. I have
> > two SQL 2000 servers running on different machines (The server is
> > running on Windows 2000 Server, and the other on Window 2000
> > Professional).
> >
> > I have created a database with one table. Have then Published this
> > database, and setup a Subscription. (The Publication is Transactional,
> > using Immediate updating.)
> >
> > If I amend/insert/delete any rows/columns at the Publisher, the
> > changes are immediately propagated to the Subscriber. The problem I'm
> > having is when the Subscriber makes any changes to the Table, SQL
> > generates the following error:
> >
> > Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Server]Could
> > not execute procedure 'sp_MSsync_upd_<tablename>_1' on remote server
> > 'SQLOLEDB'.
> >
> > I have used the Profiler, and determined that the table change
> > executes the trigger 'trg_MSsync_upd_<tablename>'. This trigger is
> > then failing when it try's to execute the following statement:
> >
> > exec @.retcode = OpenDataSource('SQLOLEDB',N'SERVER=SQLServer;UID=sa;PWD=;').[<databasename>].[dbo].[sp_MSsync_del_<tablename>_1]'
> > ...
> >
> > And since I didn't want to re-code the triggers automatically created
> > by SQL, I'm trying to figure out why the execution of the Remote
> > Stored
> > Procedure doesn't work.
> >
> > Any help is much appreciated.
> >
> > Thanks in Advance.
> > Rick 8-)
> >|||That error message means you've granted the publisher/distributer SQL Agent
account access to the subscriber machine but that the reverse is not true.
In order to do a Pull, the subscriber must have login rights to the
distributer/publisher server.
Sincerely,
Anthony Thomas
"Rick Knight" wrote:
> Thanks for the feedback Anthony, But I have check both of these, and
> still no luck. Now however the error message is different.
> Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB
> error trace [OLE/DB Provider 'SQLOLEDB' IUnknow QueryInterface
> returned 0x80070005: Access denied.
> BTW: Replication from the Publisher to the Subscriber still works okay
> though.
> Have you any other suggestions?
> Thanks in Advance
> Rick :)
>
> "AnthonyThomas" <AnthonyThomas@.discussions.microsoft.com> wrote in message news:<4DCC547D-F875-4F14-8B65-F02CD34B8088@.microsoft.com>...
> > Two things to check. First, make sure the distributor and/or the publisher
> > servers have allowed remote proc execution through sp_configure.
> >
> > Next, make sure your Win 2K Pro installation is running the SQL Server
> > service accounts under an id that has access to the distributor/publisher or
> > has the correct sign-in information.
> >
> > Sincerely,
> >
> >
> > Anthony Thomas
> >
> >
> > "Rick Knight" wrote:
> >
> > > Hi,
> > >
> > > I am experiencing some difficulties with DataBase Replication. I have
> > > two SQL 2000 servers running on different machines (The server is
> > > running on Windows 2000 Server, and the other on Window 2000
> > > Professional).
> > >
> > > I have created a database with one table. Have then Published this
> > > database, and setup a Subscription. (The Publication is Transactional,
> > > using Immediate updating.)
> > >
> > > If I amend/insert/delete any rows/columns at the Publisher, the
> > > changes are immediately propagated to the Subscriber. The problem I'm
> > > having is when the Subscriber makes any changes to the Table, SQL
> > > generates the following error:
> > >
> > > Database Error: '[Microsoft][ODBC SQL Server Driver][SQL Server]Could
> > > not execute procedure 'sp_MSsync_upd_<tablename>_1' on remote server
> > > 'SQLOLEDB'.
> > >
> > > I have used the Profiler, and determined that the table change
> > > executes the trigger 'trg_MSsync_upd_<tablename>'. This trigger is
> > > then failing when it try's to execute the following statement:
> > >
> > > exec @.retcode = OpenDataSource('SQLOLEDB',N'SERVER=SQLServer;UID=sa;PWD=;').[<databasename>].[dbo].[sp_MSsync_del_<tablename>_1]'
> > > ...
> > >
> > > And since I didn't want to re-code the triggers automatically created
> > > by SQL, I'm trying to figure out why the execution of the Remote
> > > Stored
> > > Procedure doesn't work.
> > >
> > > Any help is much appreciated.
> > >
> > > Thanks in Advance.
> > > Rick 8-)
> > >
>

Replication problem.. Please help..

Hi,
I have set up replication successfully. Data from Publisher can be
replicated to Subscriber. I can check the data directly from Enterprise
Manager.
Before replication, the application calling the database work perfectly.
HOWEVER, after replication the application cannot operate with the
replicated tables while un-changed table still works fine.
Can anyone tell me what replication has done to the table and how to avoid
it?
Thanks so much!!
Andrew,
what type of replication are you using? It sound's like it's the presence of
new (GUID) columns and/or triggers that has caused issues. If it is the GUID
columns (merge and updating subscribers) then the app should use named
column lists and in this case it'll be invisible to the App. If you have
triggers that modify the base table then this can be an issue - I'll wait
for more info before going down that route.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi Paul,
Thanks for your answer..
After checking, I found the following:
1. access right of the replicated tables are all missing;
2. all default values are missing; and
3. identity column is no longer identity column. it is just a normal column.
Do you know how to fix it?
Many Thanks.. :>
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23YlHLGPSGHA.524@.TK2MSFTNGP10.phx.gbl...
> Andrew,
> what type of replication are you using? It sound's like it's the presence
> of new (GUID) columns and/or triggers that has caused issues. If it is the
> GUID columns (merge and updating subscribers) then the app should use
> named column lists and in this case it'll be invisible to the App. If you
> have triggers that modify the base table then this can be an issue - I'll
> wait for more info before going down that route.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Andrew,
I assumed you were talking about the publisher. If it's the subscriber, you
need to open the article properties dialog screen (elipsis button) and on
the snapshot tab click the first 3 checkboxes. To get the permissions,
you'll need to add a post-snapshot script. For the identity column to remain
identity, I'd ask why? You must have set up a non-offline subscriber in
which case the identity attribute will never get used.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi Paul,
Thanks for your help.
Just found that some tables have more than 255 column and cannot pass the
vertical replication when setting the publisher. If skip those too-large
table, it works well after running the script for granting permissions.
Seems the problems is about to be solved..
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:uvPd6QaSGHA.5468@.TK2MSFTNGP14.phx.gbl...
> Andrew,
> I assumed you were talking about the publisher. If it's the subscriber,
> you need to open the article properties dialog screen (elipsis button) and
> on the snapshot tab click the first 3 checkboxes. To get the permissions,
> you'll need to add a post-snapshot script. For the identity column to
> remain identity, I'd ask why? You must have set up a non-offline
> subscriber in which case the identity attribute will never get used.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>