We are using SQL 2K with sp4 and push subscription.
If I add a trigger or a Check contraint (or other contraints) for a column
in a table that is already published in the publishing database, do or don't
I need to do anything in the subscriber database? Please explain the
consequence if I do or don't do anything in the subscriber database.
Wing
That depends on what you are trying to do. If you don't use the check
constraint and there could be DML occurring on the subscriber this check
constraint will not be enforced as it is not there.
Regarding the trigger. Do you need it fired on the subscriber as well? If
the trigger cause DML on tables which are also being replication the DML
will be replicated there as well. If not, you might want to put and fire the
trigger on the subscriber as long as all objects are there as well and the
required data is.
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
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:9F33E6B3-86D1-428E-8F9B-05F3707AEFB7@.microsoft.com...
> We are using SQL 2K with sp4 and push subscription.
> If I add a trigger or a Check contraint (or other contraints) for a column
> in a table that is already published in the publishing database, do or
> don't
> I need to do anything in the subscriber database? Please explain the
> consequence if I do or don't do anything in the subscriber database.
> Wing
|||Ok, I guess I have two scenerios.
1 Say I don't need any check contraints or triggers happening on the
subscriber server, does it mean I don't need to do anything to the subscriber
table(s). Even thought the table between the publisher and subscriber is
defferent because of the trigger and contraints, it won't cause any problem.
Am I right?
2. Say if I do want the check contraints and triggers happening on teh
subscriber server, then I will have to manually create them plus any
depending objects in the subscriber server. This is a manual process unless
I reinitialize and do a snap shot again. Am I right?
Another question too, is there a setting somewhere in replication in EM or
using sp_ stored procedure to replicate triggers or contraints?
"Wingman" wrote:
> We are using SQL 2K with sp4 and push subscription.
> If I add a trigger or a Check contraint (or other contraints) for a column
> in a table that is already published in the publishing database, do or don't
> I need to do anything in the subscriber database? Please explain the
> consequence if I do or don't do anything in the subscriber database.
> Wing
Showing posts with label push. Show all posts
Showing posts with label push. Show all posts
Thursday, March 22, 2012
Sunday, February 12, 2012
adding articles
I am using trasactional push replication on 2005.
So, first I do this:
EXEC sp_addarticle
@.publication = N'azDSS', -- Change value with the name of the
publication we wish to add to
@.article = N'tbPhxSrvrpf', -- Change value with the name of the
article we are adding
@.source_owner = N'ICOMS', -- Change value with the correct schema
name
@.source_object = N'tbPhxSrvrpf', -- Change value to the name of the
table
@.destination_table = N'tbPhxSrvrpf', -- Change value to the name of
the table
@.type = N'logbased',
@.creation_script = N'',
@.description = null,
@.pre_creation_cmd = N'truncate',
@.schema_option = 0x000000000807509F,
@.status = 16,
@.vertical_partition = N'false',
@.ins_cmd = N'CALL [sp_MSins_tbPhxSrvrpf]',-- Update the section
between the {} (and removed the {})
@.del_cmd = N'CALL [sp_MSdel_tbPhxSrvrpf]', -- Update the section
between the {} (and removed the {})
@.upd_cmd = N'SCALL [sp_MSupd_tbPhxSrvrpf]', -- Update the section
between the {} (and removed the {})
@.filter = null,
@.sync_object = null
GO
Then I do this:
exec sp_addsubscription
@.publication = N'azDSS', -- Change value with the name of the
publication
@.article = N'tbPhxSrvrpf', -- Change value with the name of the
article
@.subscriber = N'CARZ0DB13\ARZSQL13', -- Change value with the name
of the subscribing server
@.destination_db = N'azDSS', -- Change value with the name of the
subscribing db
@.sync_type = N'automatic',
@.update_mode = N'read only'
GO
and what I get is:
Msg 14100, Level 16, State 1, Procedure sp_MSrepl_addsubscription, Line
533
Specify all articles when subscribing to a publication using concurrent
snapshot processing.
Is there a work around for this. I need to be able to add an article
to an existing publication without snapshoting the entire thing
Saw this on Vyas's blog some time ago in SQL Server 2000
(http://vyaskn.tripod.com/sqlblog/).
As far as i know, you'll have to use a workaround eg have a different
publication publish the table.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Paul Ibison wrote:
> Saw this on Vyas's blog some time ago in SQL Server 2000
> (http://vyaskn.tripod.com/sqlblog/).
> As far as i know, you'll have to use a workaround eg have a different
> publication publish the table.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
Correct. I don't however see a work around posted here. I'm hoping
that someone might be able to clue me in to what I can do. I would
hate to think that MS would not have a way of adding the article to a
publication without having to do a total re-init.
-ms
|||Hi Michael, I posted an unofficial workaround in the following posting:
[url]http://groups.google.com/group/microsoft.public.sqlserver.replication/browse_frm/thread/ad9ad3d18f501332/447e9417f655bb1c?lnk=gst&q=Raymond+Mak&rnum=28#447 e9417f655bb1c[/url]
Other more official workarounds including changing the sync_method from
'concurrent' to either 'database snapshot' (enterprise edition only) and
'native' (which locks table during snapshot generation). Change the
sync_method will force a reinitialization of all your subscriptions at this
point.
-Raymond
"michael.swinarski@.cox.com" <mswinarski@.gmail.com> wrote in message
news:1162309836.937305.115900@.k70g2000cwa.googlegr oups.com...
> Paul Ibison wrote:
>
> Correct. I don't however see a work around posted here. I'm hoping
> that someone might be able to clue me in to what I can do. I would
> hate to think that MS would not have a way of adding the article to a
> publication without having to do a total re-init.
> -ms
>
|||This publication is over 200 GB. I would rather not have to
re-snapshot the entire publication just to add a table (wich we will be
doing more offtien then most). Can this be done?
Raymond Mak [MSFT] wrote:[vbcol=seagreen]
> Hi Michael, I posted an unofficial workaround in the following posting:
> [url]http://groups.google.com/group/microsoft.public.sqlserver.replication/browse_frm/thread/ad9ad3d18f501332/447e9417f655bb1c?lnk=gst&q=Raymond+Mak&rnum=28#447 e9417f655bb1c[/url]
> Other more official workarounds including changing the sync_method from
> 'concurrent' to either 'database snapshot' (enterprise edition only) and
> 'native' (which locks table during snapshot generation). Change the
> sync_method will force a reinitialization of all your subscriptions at this
> point.
> -Raymond
> "michael.swinarski@.cox.com" <mswinarski@.gmail.com> wrote in message
> news:1162309836.937305.115900@.k70g2000cwa.googlegr oups.com...
|||I am guessing that you don't want the snapshot agent to regenerate snapshot
data for all articles in your publication. If this is the case, please make
sure that the immediate_sync property in syspublications is set to 0 (see
sp_changepublication).
-Raymond
"michael.swinarski@.cox.com" <mswinarski@.gmail.com> wrote in message
news:1162316002.881015.11340@.m7g2000cwm.googlegrou ps.com...
> This publication is over 200 GB. I would rather not have to
> re-snapshot the entire publication just to add a table (wich we will be
> doing more offtien then most). Can this be done?
>
>
> Raymond Mak [MSFT] wrote:
>
|||Can you then generate a snapshot for the individual article? When the
article is added, how does the subscriber recieve it for the first
time?
-ms
Raymond Mak [MSFT] wrote:[vbcol=seagreen]
> I am guessing that you don't want the snapshot agent to regenerate snapshot
> data for all articles in your publication. If this is the case, please make
> sure that the immediate_sync property in syspublications is set to 0 (see
> sp_changepublication).
> -Raymond
> "michael.swinarski@.cox.com" <mswinarski@.gmail.com> wrote in message
> news:1162316002.881015.11340@.m7g2000cwm.googlegrou ps.com...
|||By setting the immediate_sync property to 0, the snapshot agent should only
generate files for articles with uninitialized subscriptions.
-Raymond
"michael.swinarski@.cox.com" <mswinarski@.gmail.com> wrote in message
news:1162327020.094451.305790@.k70g2000cwa.googlegr oups.com...
> Can you then generate a snapshot for the individual article? When the
> article is added, how does the subscriber recieve it for the first
> time?
> -ms
>
>
> Raymond Mak [MSFT] wrote:
>
So, first I do this:
EXEC sp_addarticle
@.publication = N'azDSS', -- Change value with the name of the
publication we wish to add to
@.article = N'tbPhxSrvrpf', -- Change value with the name of the
article we are adding
@.source_owner = N'ICOMS', -- Change value with the correct schema
name
@.source_object = N'tbPhxSrvrpf', -- Change value to the name of the
table
@.destination_table = N'tbPhxSrvrpf', -- Change value to the name of
the table
@.type = N'logbased',
@.creation_script = N'',
@.description = null,
@.pre_creation_cmd = N'truncate',
@.schema_option = 0x000000000807509F,
@.status = 16,
@.vertical_partition = N'false',
@.ins_cmd = N'CALL [sp_MSins_tbPhxSrvrpf]',-- Update the section
between the {} (and removed the {})
@.del_cmd = N'CALL [sp_MSdel_tbPhxSrvrpf]', -- Update the section
between the {} (and removed the {})
@.upd_cmd = N'SCALL [sp_MSupd_tbPhxSrvrpf]', -- Update the section
between the {} (and removed the {})
@.filter = null,
@.sync_object = null
GO
Then I do this:
exec sp_addsubscription
@.publication = N'azDSS', -- Change value with the name of the
publication
@.article = N'tbPhxSrvrpf', -- Change value with the name of the
article
@.subscriber = N'CARZ0DB13\ARZSQL13', -- Change value with the name
of the subscribing server
@.destination_db = N'azDSS', -- Change value with the name of the
subscribing db
@.sync_type = N'automatic',
@.update_mode = N'read only'
GO
and what I get is:
Msg 14100, Level 16, State 1, Procedure sp_MSrepl_addsubscription, Line
533
Specify all articles when subscribing to a publication using concurrent
snapshot processing.
Is there a work around for this. I need to be able to add an article
to an existing publication without snapshoting the entire thing
Saw this on Vyas's blog some time ago in SQL Server 2000
(http://vyaskn.tripod.com/sqlblog/).
As far as i know, you'll have to use a workaround eg have a different
publication publish the table.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Paul Ibison wrote:
> Saw this on Vyas's blog some time ago in SQL Server 2000
> (http://vyaskn.tripod.com/sqlblog/).
> As far as i know, you'll have to use a workaround eg have a different
> publication publish the table.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
Correct. I don't however see a work around posted here. I'm hoping
that someone might be able to clue me in to what I can do. I would
hate to think that MS would not have a way of adding the article to a
publication without having to do a total re-init.
-ms
|||Hi Michael, I posted an unofficial workaround in the following posting:
[url]http://groups.google.com/group/microsoft.public.sqlserver.replication/browse_frm/thread/ad9ad3d18f501332/447e9417f655bb1c?lnk=gst&q=Raymond+Mak&rnum=28#447 e9417f655bb1c[/url]
Other more official workarounds including changing the sync_method from
'concurrent' to either 'database snapshot' (enterprise edition only) and
'native' (which locks table during snapshot generation). Change the
sync_method will force a reinitialization of all your subscriptions at this
point.
-Raymond
"michael.swinarski@.cox.com" <mswinarski@.gmail.com> wrote in message
news:1162309836.937305.115900@.k70g2000cwa.googlegr oups.com...
> Paul Ibison wrote:
>
> Correct. I don't however see a work around posted here. I'm hoping
> that someone might be able to clue me in to what I can do. I would
> hate to think that MS would not have a way of adding the article to a
> publication without having to do a total re-init.
> -ms
>
|||This publication is over 200 GB. I would rather not have to
re-snapshot the entire publication just to add a table (wich we will be
doing more offtien then most). Can this be done?
Raymond Mak [MSFT] wrote:[vbcol=seagreen]
> Hi Michael, I posted an unofficial workaround in the following posting:
> [url]http://groups.google.com/group/microsoft.public.sqlserver.replication/browse_frm/thread/ad9ad3d18f501332/447e9417f655bb1c?lnk=gst&q=Raymond+Mak&rnum=28#447 e9417f655bb1c[/url]
> Other more official workarounds including changing the sync_method from
> 'concurrent' to either 'database snapshot' (enterprise edition only) and
> 'native' (which locks table during snapshot generation). Change the
> sync_method will force a reinitialization of all your subscriptions at this
> point.
> -Raymond
> "michael.swinarski@.cox.com" <mswinarski@.gmail.com> wrote in message
> news:1162309836.937305.115900@.k70g2000cwa.googlegr oups.com...
|||I am guessing that you don't want the snapshot agent to regenerate snapshot
data for all articles in your publication. If this is the case, please make
sure that the immediate_sync property in syspublications is set to 0 (see
sp_changepublication).
-Raymond
"michael.swinarski@.cox.com" <mswinarski@.gmail.com> wrote in message
news:1162316002.881015.11340@.m7g2000cwm.googlegrou ps.com...
> This publication is over 200 GB. I would rather not have to
> re-snapshot the entire publication just to add a table (wich we will be
> doing more offtien then most). Can this be done?
>
>
> Raymond Mak [MSFT] wrote:
>
|||Can you then generate a snapshot for the individual article? When the
article is added, how does the subscriber recieve it for the first
time?
-ms
Raymond Mak [MSFT] wrote:[vbcol=seagreen]
> I am guessing that you don't want the snapshot agent to regenerate snapshot
> data for all articles in your publication. If this is the case, please make
> sure that the immediate_sync property in syspublications is set to 0 (see
> sp_changepublication).
> -Raymond
> "michael.swinarski@.cox.com" <mswinarski@.gmail.com> wrote in message
> news:1162316002.881015.11340@.m7g2000cwm.googlegrou ps.com...
|||By setting the immediate_sync property to 0, the snapshot agent should only
generate files for articles with uninitialized subscriptions.
-Raymond
"michael.swinarski@.cox.com" <mswinarski@.gmail.com> wrote in message
news:1162327020.094451.305790@.k70g2000cwa.googlegr oups.com...
> Can you then generate a snapshot for the individual article? When the
> article is added, how does the subscriber recieve it for the first
> time?
> -ms
>
>
> Raymond Mak [MSFT] wrote:
>
Adding Article/Table!
Hello All,
I'm using Transactional Replication and it's Push subscription.
Can you plz give me the complete steps to add a single table w/o starting
snapshot for all tables.
And another question,
BOL says sp_refreshsubscription for Pull and
sp_reinitsubscription is for Push Subscription.
But I saw newgroup an it says BOL is wrong sp_refreshsubscription works for
both.
What is the difference b/w sp_refreshsubscription and
sp_reinitsubscription?
Thanks in advance.
Naveed.
I just tried to do this:
sp_addarticle 'pubs','jobs','jobs'
I then generated my snapshot - and restarted my distribution agent. Only the
jobs table went over in the new snapshot.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Naveed" <nrehman@.marsonssoft.com> wrote in message
news:OqzXJ94qEHA.3900@.TK2MSFTNGP10.phx.gbl...
> Hello All,
> I'm using Transactional Replication and it's Push subscription.
> Can you plz give me the complete steps to add a single table w/o starting
> snapshot for all tables.
> And another question,
> BOL says sp_refreshsubscription for Pull and
> sp_reinitsubscription is for Push Subscription.
> But I saw newgroup an it says BOL is wrong sp_refreshsubscription works
for
> both.
> What is the difference b/w sp_refreshsubscription and
> sp_reinitsubscription?
> Thanks in advance.
> Naveed.
>
>
I'm using Transactional Replication and it's Push subscription.
Can you plz give me the complete steps to add a single table w/o starting
snapshot for all tables.
And another question,
BOL says sp_refreshsubscription for Pull and
sp_reinitsubscription is for Push Subscription.
But I saw newgroup an it says BOL is wrong sp_refreshsubscription works for
both.
What is the difference b/w sp_refreshsubscription and
sp_reinitsubscription?
Thanks in advance.
Naveed.
I just tried to do this:
sp_addarticle 'pubs','jobs','jobs'
I then generated my snapshot - and restarted my distribution agent. Only the
jobs table went over in the new snapshot.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Naveed" <nrehman@.marsonssoft.com> wrote in message
news:OqzXJ94qEHA.3900@.TK2MSFTNGP10.phx.gbl...
> Hello All,
> I'm using Transactional Replication and it's Push subscription.
> Can you plz give me the complete steps to add a single table w/o starting
> snapshot for all tables.
> And another question,
> BOL says sp_refreshsubscription for Pull and
> sp_reinitsubscription is for Push Subscription.
> But I saw newgroup an it says BOL is wrong sp_refreshsubscription works
for
> both.
> What is the difference b/w sp_refreshsubscription and
> sp_reinitsubscription?
> Thanks in advance.
> Naveed.
>
>
Thursday, February 9, 2012
Adding a table, stored procedure, or view in push tranaction repl
We are using SQL 2k and use push replication. If I want to add a table, a
view or a stored procedure to a publishing table, view or stored procedure,
can I just create them using EM or query analyzer manually in both the
publishing table or subscribing table without involving replication?
If this is not a good way, what can I do to just push the new object over
without doing a snapshot?
Wing
Yes you can create them on both sides, but the table will not be
synchronized or kept current. To do this you need to use sp_addarticle.
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
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:982C7152-AF5A-4E21-A2E0-58A48C894FBC@.microsoft.com...
> We are using SQL 2k and use push replication. If I want to add a table, a
> view or a stored procedure to a publishing table, view or stored
> procedure,
> can I just create them using EM or query analyzer manually in both the
> publishing table or subscribing table without involving replication?
> If this is not a good way, what can I do to just push the new object over
> without doing a snapshot?
> Wing
|||You can create the article on the publisher as per usual then use
sp_addarticle and sp_addsubscription followed by running the snapshot agent
and distribution agent. You mention that you don't want a new snapshot, but
in the case of transactional replication, running the snapshot agent in this
case will just create a snapshot of the new article and not all the others.
exec sp_addarticle @.publication = 'tTestFNames'
, @.article = 'tEmployees'
, @.source_table = 'tEmployees'
exec sp_addsubscription @.publication = 'tTestFNames'
, @.article = 'tEmployees'
, @.subscriber = 'RSCOMPUTER'
, @.destination_db = 'testrep'
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||We will be running a merge replication to multiple laptop subscribers. Will
this same concept apply to us? e.g. would we run the sp_addarticle and
sp_addsubscription ? And would we need to run a new snapshot?
Also, is there a way to retrieve all of the names of the subscribers for a
publication? Thanks.
David
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23wsrAKhDGHA.3820@.TK2MSFTNGP12.phx.gbl...
> You can create the article on the publisher as per usual then use
> sp_addarticle and sp_addsubscription followed by running the snapshot
> agent and distribution agent. You mention that you don't want a new
> snapshot, but in the case of transactional replication, running the
> snapshot agent in this case will just create a snapshot of the new article
> and not all the others.
> exec sp_addarticle @.publication = 'tTestFNames'
> , @.article = 'tEmployees'
> , @.source_table = 'tEmployees'
> exec sp_addsubscription @.publication = 'tTestFNames'
> , @.article = 'tEmployees'
> , @.subscriber = 'RSCOMPUTER'
> , @.destination_db = 'testrep'
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||You use sp_addmergearticle. A new snapshot is generated. IIRC if the article
is part of a join filter an entire new snapshot will be genereated.
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
"David Chase" <dlchase@.lifetimeinc.com> wrote in message
news:uXjH6cvDGHA.1676@.TK2MSFTNGP09.phx.gbl...
> We will be running a merge replication to multiple laptop subscribers.
> Will this same concept apply to us? e.g. would we run the sp_addarticle
> and sp_addsubscription ? And would we need to run a new snapshot?
> Also, is there a way to retrieve all of the names of the subscribers for a
> publication? Thanks.
> David
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
> news:%23wsrAKhDGHA.3820@.TK2MSFTNGP12.phx.gbl...
>
|||David,
try sp_helpsubscription for the list of subscriptions.
For merge you can use sp_addmergearticle or just add the article through the
publication properties dialog box. You'll still need to run the snapshot
agent but it works differently and a whole snapshot is generated, even
though only the new article is applied by the merge agent.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||A new snapshot of your entire merge publication is always forced.
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
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eZF%23FgvDGHA.3828@.TK2MSFTNGP14.phx.gbl...
> You use sp_addmergearticle. A new snapshot is generated. IIRC if the
> article is part of a join filter an entire new snapshot will be
> genereated.
> --
> 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
> "David Chase" <dlchase@.lifetimeinc.com> wrote in message
> news:uXjH6cvDGHA.1676@.TK2MSFTNGP09.phx.gbl...
>
view or a stored procedure to a publishing table, view or stored procedure,
can I just create them using EM or query analyzer manually in both the
publishing table or subscribing table without involving replication?
If this is not a good way, what can I do to just push the new object over
without doing a snapshot?
Wing
Yes you can create them on both sides, but the table will not be
synchronized or kept current. To do this you need to use sp_addarticle.
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
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:982C7152-AF5A-4E21-A2E0-58A48C894FBC@.microsoft.com...
> We are using SQL 2k and use push replication. If I want to add a table, a
> view or a stored procedure to a publishing table, view or stored
> procedure,
> can I just create them using EM or query analyzer manually in both the
> publishing table or subscribing table without involving replication?
> If this is not a good way, what can I do to just push the new object over
> without doing a snapshot?
> Wing
|||You can create the article on the publisher as per usual then use
sp_addarticle and sp_addsubscription followed by running the snapshot agent
and distribution agent. You mention that you don't want a new snapshot, but
in the case of transactional replication, running the snapshot agent in this
case will just create a snapshot of the new article and not all the others.
exec sp_addarticle @.publication = 'tTestFNames'
, @.article = 'tEmployees'
, @.source_table = 'tEmployees'
exec sp_addsubscription @.publication = 'tTestFNames'
, @.article = 'tEmployees'
, @.subscriber = 'RSCOMPUTER'
, @.destination_db = 'testrep'
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||We will be running a merge replication to multiple laptop subscribers. Will
this same concept apply to us? e.g. would we run the sp_addarticle and
sp_addsubscription ? And would we need to run a new snapshot?
Also, is there a way to retrieve all of the names of the subscribers for a
publication? Thanks.
David
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23wsrAKhDGHA.3820@.TK2MSFTNGP12.phx.gbl...
> You can create the article on the publisher as per usual then use
> sp_addarticle and sp_addsubscription followed by running the snapshot
> agent and distribution agent. You mention that you don't want a new
> snapshot, but in the case of transactional replication, running the
> snapshot agent in this case will just create a snapshot of the new article
> and not all the others.
> exec sp_addarticle @.publication = 'tTestFNames'
> , @.article = 'tEmployees'
> , @.source_table = 'tEmployees'
> exec sp_addsubscription @.publication = 'tTestFNames'
> , @.article = 'tEmployees'
> , @.subscriber = 'RSCOMPUTER'
> , @.destination_db = 'testrep'
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||You use sp_addmergearticle. A new snapshot is generated. IIRC if the article
is part of a join filter an entire new snapshot will be genereated.
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
"David Chase" <dlchase@.lifetimeinc.com> wrote in message
news:uXjH6cvDGHA.1676@.TK2MSFTNGP09.phx.gbl...
> We will be running a merge replication to multiple laptop subscribers.
> Will this same concept apply to us? e.g. would we run the sp_addarticle
> and sp_addsubscription ? And would we need to run a new snapshot?
> Also, is there a way to retrieve all of the names of the subscribers for a
> publication? Thanks.
> David
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
> news:%23wsrAKhDGHA.3820@.TK2MSFTNGP12.phx.gbl...
>
|||David,
try sp_helpsubscription for the list of subscriptions.
For merge you can use sp_addmergearticle or just add the article through the
publication properties dialog box. You'll still need to run the snapshot
agent but it works differently and a whole snapshot is generated, even
though only the new article is applied by the merge agent.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||A new snapshot of your entire merge publication is always forced.
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
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eZF%23FgvDGHA.3828@.TK2MSFTNGP14.phx.gbl...
> You use sp_addmergearticle. A new snapshot is generated. IIRC if the
> article is part of a join filter an entire new snapshot will be
> genereated.
> --
> 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
> "David Chase" <dlchase@.lifetimeinc.com> wrote in message
> news:uXjH6cvDGHA.1676@.TK2MSFTNGP09.phx.gbl...
>
Subscribe to:
Posts (Atom)