You should not use this procedure. This procedure is used by the logreader when it reads transactions from the log, writes them to the distribution database, and then marks these...

I've done over 1000. It gets complex when you have to replicate a lot of data. Replicating a lot of objects is not problematic.

Hilary Cotter

Looking for a SQL Server replication...

do this

sp_changepublication 'PublicationName', 'status','active'

--

Hilary Cotter

Looking for a book on SQL Server replication?

http://www.nwsu.com/0974973602.html

If at all possible use change tracking instead of full or incremental populations.

In your search query limit the amount of rows returned. This is the single greatest thing you can...

Yes, that is rather confusing. What it should say is give as much memory as possible to SQL Server, but leave 512 Mgs for the OS and MSSearch.

MSSearch will consume...

have a look at

http://support.microsoft.com/default.aspx?scid=kb;en-us;240867&Product=sql2k

--

Hilary Cotter

Looking for a book on SQL Server replication?

http://www.nwsu.com/0974973602.html

have a look at replication alerts to warn you when the distribution agent fails.

--

Hilary Cotter

Looking for a book on SQL Server replication?

http://www.nwsu.com/0974973602.html

No. The network folks will have to measure throughput, that's their job. You can tell them the number of commands by a query like this in your distribution database.

select...

in your publication database issue the below query

sp_scriptpublicationcustomprocs ‘PublicationName’

Then copy what appears in your results pane into query analyzer connected to your subscription database and execute it. Restart your...

what about using sp_repladdcolumn and sp_repldropcolumn? This is MS preferred way of making changes to the schema of replicated tables.