Replication sql 2000 question

If i add NEW COLUMNS to 2-3 existing Articles\Tables using
"sp_repladdcolumn" do i have to re-initialize replication & apply
SNAPSHOT or LOG READER will apply all data in that new columns for
subscriber. i am trying to understand when i add new columns how
columns are getting replicated to SUBSCRIBER & how data will be copied
to new columns.
Any help is appreciated to make me understand & thanking experts in
advance.
Provided you're not intending to modify the PK in trans replication (in
which case it won't work anyway) there's no need to reinitialize. The
columns will be nullable initially and there will be no data in them.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||If DDL replication is turned on do you need to use sp_repladdcolumn?
On 4 Feb 2007 21:34:05 -0800, myrights99@.gmail.com wrote:

>If i add NEW COLUMNS to 2-3 existing Articles\Tables using
>"sp_repladdcolumn" do i have to re-initialize replication & apply
>SNAPSHOT or LOG READER will apply all data in that new columns for
>subscriber. i am trying to understand when i add new columns how
>columns are getting replicated to SUBSCRIBER & how data will be copied
>to new columns.
>Any help is appreciated to make me understand & thanking experts in
>advance.
|||In most cases a mini-snapshot of only the modified article will be generated
and sent to all named subscribers.
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
<myrights99@.gmail.com> wrote in message
news:1170653645.410658.238120@.m58g2000cwm.googlegr oups.com...
> If i add NEW COLUMNS to 2-3 existing Articles\Tables using
> "sp_repladdcolumn" do i have to re-initialize replication & apply
> SNAPSHOT or LOG READER will apply all data in that new columns for
> subscriber. i am trying to understand when i add new columns how
> columns are getting replicated to SUBSCRIBER & how data will be copied
> to new columns.
> Any help is appreciated to make me understand & thanking experts in
> advance.
>

Replication Question

Hi,

I am trying to set-up a transactional replication.

1. Created a Publication with 1 table containing only the first four columns (out of 10 columns).

2. When I create a subscription, how do I map the Publication Columns to Subscription columns? In my subscriber DB, I need different column names. I don't get an option to map the columns ...

How do I do it? TIA.

1. To create article with part of columns, please refer to Books On line, title <To define a column filter for an article published in a snapshot or transactional publication>

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/repref9/html/504fd568-13ae-4dc4-88da-950c1ec1e8c1.htm

2. Subscription can have table name different to published table name, but columns name has to be same.

Thanks

Yunjing

Replication problem after reduce no of columns to less than 254

There was a replication problem between db1 and db3. The scenario is that a
table was added with more than 254 nos. of columns. An error
[Error 2757: RAISERROR failed due to invalid parameter substitution(s) for
error 20068, severity 16, state 1]
is prompted during the creation of publication for the replication.
Therefore, the new added columns are deleted. However, there is another
error [Error 220: Arithmetic overflow error for data type tinyint, value =
256.]
is prompted when the publication for the replication was created again.
How to fix this error?
David NG
can I see the schema for this reduced table? How many columns did it have
originally?
http://www.zetainteractive.com - Shift Happens!
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
"David NG" <David NG@.discussions.microsoft.com> wrote in message
news:384758F8-4985-4566-B8C0-7532A0C7DFC3@.microsoft.com...
> There was a replication problem between db1 and db3. The scenario is that
> a
> table was added with more than 254 nos. of columns. An error
> [Error 2757: RAISERROR failed due to invalid parameter substitution(s) for
> error 20068, severity 16, state 1]
> is prompted during the creation of publication for the replication.
>
> Therefore, the new added columns are deleted. However, there is another
> error [Error 220: Arithmetic overflow error for data type tinyint, value =
> 256.]
> is prompted when the publication for the replication was created again.
> How to fix this error?
> David NG
>

Replication problem

How to perform replication suppose on two tables but NOT for all columns'
Suppose if i have IDENTITY column in table i can use option NOT FOR
REPLICATION, however in case my column doesn't identity, so '
Message posted via http://www.webservertalk.comI THINK IT'S ONLY FOR identity COLUMNS
Message posted via http://www.webservertalk.com

Replication object changes

Does replication allow object changes? I read that in SQL server 2000 it will
update new columns on the Publisher and push them to the subscriber, but does
that mean if create a new stored proc on the publisher it will push that as
well to the subscriber? Thanks!
Anita,
for a new stored proc, you could add it to an existing publication, snapshot
and distribute, or create a new publication. A new Stored Proc won't be
picked up automatically. Also, sp_addscriptexec can be used to propagate to
all subscribersif you just want to get it there. Remember that changes to
the stored proc tsql are not picked up and propagated - we need sql 2005 for
this.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanks Paul!
"Paul Ibison" wrote:

> Anita,
> for a new stored proc, you could add it to an existing publication, snapshot
> and distribute, or create a new publication. A new Stored Proc won't be
> picked up automatically. Also, sp_addscriptexec can be used to propagate to
> all subscribersif you just want to get it there. Remember that changes to
> the stored proc tsql are not picked up and propagated - we need sql 2005 for
> this.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>