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.
>
Showing posts with label sp_repladdcolumn. Show all posts
Showing posts with label sp_repladdcolumn. Show all posts
Wednesday, March 28, 2012
Replication sql 2000 question
Labels:
2-3,
applysnapshot,
articles,
columns,
database,
existing,
log,
microsoft,
mysql,
oracle,
re-initialize,
replication,
server,
sp_repladdcolumn,
sql,
tables
Tuesday, March 20, 2012
Replication problem
Hi folks; i have added a column into a published table using SP_REPLADDCOLUMN.
I get the following message:
Warning: The table 'MY_TABLE' has been created but its maximum row size (8814) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.
Warning: The table 'aonflict_MBDB_PUBLICATION_PTL_PATIENT_CLAIM' has been created but its maximum row size (10801) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.
MY_TABLE had 40 columns.
Is there any maximum limit of allowed columns in a published table?
Can anyone explain what are the concequences!I dont think the message you are receiving is related to replication
The 8060 byte limit is a universal limit for the data size of a row. It relates to the maximum amount of data that can be stored on a page.
I get the following message:
Warning: The table 'MY_TABLE' has been created but its maximum row size (8814) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.
Warning: The table 'aonflict_MBDB_PUBLICATION_PTL_PATIENT_CLAIM' has been created but its maximum row size (10801) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.
MY_TABLE had 40 columns.
Is there any maximum limit of allowed columns in a published table?
Can anyone explain what are the concequences!I dont think the message you are receiving is related to replication
The 8060 byte limit is a universal limit for the data size of a row. It relates to the maximum amount of data that can be stored on a page.
Labels:
column,
database,
folks,
following,
messagewarning,
microsoft,
my_table,
mysql,
oracle,
published,
replication,
server,
sp_repladdcolumn,
sql,
table
Subscribe to:
Posts (Atom)