October 15, 2004 at 10:19 am
SQL Server 2000
Transactional Replication in QA environment
New column is not showing up in the subscription database.
Added article..............
exec sp_addarticle @publication = N'USWCITCQ to USWCITCR',
@article = N'tblTemplateCertHolder',
@source_owner = N'dbo',
@source_object = N'tblTemplateCertHolder',
@destination_table = N'tblTemplateCertHolder',
@type = N'logbased',
@creation_script = null,
@description = null,
@pre_creation_cmd = N'drop',
@schema_option = 0x00000000000000F3,
@status = 16,
@vertical_partition = N'false',
@ins_cmd = N'CALL sp_MSins_tblTemplateCertHolder',
@del_cmd = N'CALL sp_MSdel_tblTemplateCertHolder',
@upd_cmd = N'MCALL sp_MSupd_tblTemplateCertHolder',
@filter = null,
@sync_object = null,
@auto_identity_range = N'false'
GO
Added Column...........
exec sp_repladdcolumn @source_object = 'tblTemplateCertHolder',
@column = 'sCHAttention',
@typetext = 'char (60)',
@publication_to_add = 'USWCITCQ to USWCITCR',
@force_invalidate_snapshot = 1,
@force_reinit_subscription = 1
Ran the snapshot agent and the changes didn't go across. Is there someway to move the changes across to the subscription database? Thanks...Jeff
"Keep Your Stick On the Ice" ..Red Green
October 15, 2004 at 11:31 am
I have always added a column with that sp, after the snapshot was applied. Because sp_repladdcolumn add a column at the publisher and the subscriber when the distribution agent runs.
Try to force again the distribution agent to check if the add column is pending as a transaction.
October 15, 2004 at 1:08 pm
Thanks... I needed to run sp_addsubscription. After doing that everything was fine 🙂
"Keep Your Stick On the Ice" ..Red Green
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply