How can I make changes to my Publisher tables e.g change columns ,

I have a transactional replication with one publisher and one subscriber.
This is working fine. Now my developers need to make changes to the
production database. They would like to change columns, add new indexes, etc.
What is the bet way to do this without much down time?
George Gopie
freaking developers. You can use sp_repladdcolumn or sp_repldropcolumn for
changing columns. To add new indexes use sp_addscriptexec for subscriptions
deployed via unc's.
If your environment's schema is volatile (i.e. changing all the time) you
should look at log shipping or SQL Server 2005.
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
"georgeg" <ggg@.hotamil.com> wrote in message
news:B980F6D1-CF64-4A7D-B513-9715D427A898@.microsoft.com...
> I have a transactional replication with one publisher and one subscriber.
> This is working fine. Now my developers need to make changes to the
> production database. They would like to change columns, add new indexes,
etc.
> What is the bet way to do this without much down time?
> --
> George Gopie
>

How can I get the BCP's to run on the Distributor?

After extensive testing I have found that bcp's run almost twice as fast on my dedicated Distributor than on either the Publisher or Subscriber. I was wondering if there is a way to make the bcp's spawned by creating a Snapshot run on the distributor and not the Publisher.

Any comments?

I am not sure what you are really after but the snapshot agent (hence all the bcp threads, we don't launch separate bcp.exe processes) is supposed to run on the distributor so I am probably just getting it all wrong

- Raymond

How can I get a (count) of how many transactions the log reader is wating on?

I need to know if replication is running behind. I have already queried
with distribution db for this subscriber , but it's telling me there are
no transactions waiting.
the agent history on the log reader shows it moving across data to the
distributor normally, but when i try to shrink the translog its telling
me that it can't because there are transactions marked for rpelication
that have not been pushed over yet.
here's what I ran on the distrbutor to get the trasnactions waiting
Select * from dbo.MSpublisher_databases where publisher_db = 'cpk01'
(to get publisher id)
then
Select count(1) from dbo.MSrepl_transactions where
publisher_database_id = 13
(to get transaction count)
tia
-comb
Comb,
querying this view (distribution database) is what you need:
MSdistribution_status.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||In article <Ochx0lzBGHA.140@.TK2MSFTNGP12.phx.gbl>,
Paul.Ibison@.Pygmalion.Com says...
> Comb,
> querying this view (distribution database) is what you need:
> MSdistribution_status.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
Thanks Paul.
-comb