Can subscribers pick and choose articles?

Can a subscription of a snapshot publication containing 2 or more articles
choose which articles it wants? For example, if the publication has 5
articles published, and the subscriber only wants 3 of them, can the
subscriber specify the 3 or does it have to take all 5?
I know this cannot be achieved using the wizards but I believe it is an
option when you use the stored procedures. I would appreciate some info on
this.
BTW, I am using SQL 2005. Thanks!
Johnny,
for transactional replication, have a look at the following types of script:
exec sp_dropsubscription @.publication = 'tTestFNames'
, @.article = 'tEmployees'
, @.subscriber = 'RSCOMPUTER'
, @.destination_db = 'testrep'
exec sp_addsubscription @.publication = 'tTestFNames'
, @.article = 'tEmployees'
, @.subscriber = 'RSCOMPUTER'
, @.destination_db = 'testrep'
The obvious caveat would be that your system becomes less maintainable this
way.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I am using snapshot replication. Do you recommend I create separate
publications instead on all in one?
"Paul Ibison" wrote:

> Johnny,
> for transactional replication, have a look at the following types of script:
> exec sp_dropsubscription @.publication = 'tTestFNames'
> , @.article = 'tEmployees'
> , @.subscriber = 'RSCOMPUTER'
> , @.destination_db = 'testrep'
> exec sp_addsubscription @.publication = 'tTestFNames'
> , @.article = 'tEmployees'
> , @.subscriber = 'RSCOMPUTER'
> , @.destination_db = 'testrep'
> The obvious caveat would be that your system becomes less maintainable this
> way.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Johnny,
this should also work for snapshot (merge is the exception), however, I'd
recommend separate publications as it'll be more 'visible' in terms of
management. The downside is that You'll be locking the tables on the
publisher twice instead of once.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Can replication be ran on a MS sharepoint database?

Hello,

I was curious if you can have merge and/or snapshot replication setup on a MS sharepoint database? Thanks.

John

I don't think that those will work for the following reason.

At a recent MS course, we asked our instructor if it was possible to change the content database in SP central Admin to a secondary database server during a crisis. They advised that this might be a problem because the SP configuration database creates hard-coded entries referencing the database server name that it resides on. They suspsected that these entries would cause problems in the long run, if not right away.

We decided to test this out by creating a virtual environment that mimicked our production system. We then copied the database to a seperate physical machine. To try and avoid the configuration database problems, we created a new virtual site on the VM that mirrored our existing front end and pointed it to the new database to recreate the configuration database.

Everything worked okay for about 3 hours then we began to see timeouts due to maxpoolsize being reached. When we checked the event log we also found that the server was STILL trying to connect to the original database even though everything was on the new server. Eventually, it became impossible to access any of the sites in the virtual environment.

I imagine that these entries in the configuration database would cause the same problem if we were to replicate from one server to another. We're now thinking of using log shipping or clustering to try and provide the redundancy we're looking for.

|||

Jaydog,

Thanks for your reply.

John

|||Hey John,

Looks like I was premature with my first response. We tried the same thing one more time, except that we shut down the old SQL Server before clearing the old configuration database and allowing SharePoint to rebuild it. So far, it looks like everything is up and running.

We're giving it a few days to see if there are any adverse effects and then we will be trying to get merge replication up and running. I'll post again once there is more to report.|||

Jaydog,

I look forward to what you find out.

John

|||

Jaydog,

I was curious if you had an update on this?

John

|||

Jaydog,

I would also be interested in finding out how that went.

JBW

Can replication be ran on a MS sharepoint database?

Hello,

I was curious if you can have merge and/or snapshot replication setup on a MS sharepoint database? Thanks.

John

I don't think that those will work for the following reason.

At a recent MS course, we asked our instructor if it was possible to change the content database in SP central Admin to a secondary database server during a crisis. They advised that this might be a problem because the SP configuration database creates hard-coded entries referencing the database server name that it resides on. They suspsected that these entries would cause problems in the long run, if not right away.

We decided to test this out by creating a virtual environment that mimicked our production system. We then copied the database to a seperate physical machine. To try and avoid the configuration database problems, we created a new virtual site on the VM that mirrored our existing front end and pointed it to the new database to recreate the configuration database.

Everything worked okay for about 3 hours then we began to see timeouts due to maxpoolsize being reached. When we checked the event log we also found that the server was STILL trying to connect to the original database even though everything was on the new server. Eventually, it became impossible to access any of the sites in the virtual environment.

I imagine that these entries in the configuration database would cause the same problem if we were to replicate from one server to another. We're now thinking of using log shipping or clustering to try and provide the redundancy we're looking for.

|||

Jaydog,

Thanks for your reply.

John

|||Hey John,

Looks like I was premature with my first response. We tried the same thing one more time, except that we shut down the old SQL Server before clearing the old configuration database and allowing SharePoint to rebuild it. So far, it looks like everything is up and running.

We're giving it a few days to see if there are any adverse effects and then we will be trying to get merge replication up and running. I'll post again once there is more to report.
|||

Jaydog,

I look forward to what you find out.

John

|||

Jaydog,

I was curious if you had an update on this?

John

|||

Jaydog,

I would also be interested in finding out how that went.

JBW

Can replication be ran on a MS sharepoint database?

Hello,

I was curious if you can have merge and/or snapshot replication setup on a MS sharepoint database? Thanks.

John

I don't think that those will work for the following reason.

At a recent MS course, we asked our instructor if it was possible to change the content database in SP central Admin to a secondary database server during a crisis. They advised that this might be a problem because the SP configuration database creates hard-coded entries referencing the database server name that it resides on. They suspsected that these entries would cause problems in the long run, if not right away.

We decided to test this out by creating a virtual environment that mimicked our production system. We then copied the database to a seperate physical machine. To try and avoid the configuration database problems, we created a new virtual site on the VM that mirrored our existing front end and pointed it to the new database to recreate the configuration database.

Everything worked okay for about 3 hours then we began to see timeouts due to maxpoolsize being reached. When we checked the event log we also found that the server was STILL trying to connect to the original database even though everything was on the new server. Eventually, it became impossible to access any of the sites in the virtual environment.

I imagine that these entries in the configuration database would cause the same problem if we were to replicate from one server to another. We're now thinking of using log shipping or clustering to try and provide the redundancy we're looking for.

|||

Jaydog,

Thanks for your reply.

John

|||Hey John,

Looks like I was premature with my first response. We tried the same thing one more time, except that we shut down the old SQL Server before clearing the old configuration database and allowing SharePoint to rebuild it. So far, it looks like everything is up and running.

We're giving it a few days to see if there are any adverse effects and then we will be trying to get merge replication up and running. I'll post again once there is more to report.|||

Jaydog,

I look forward to what you find out.

John

|||

Jaydog,

I was curious if you had an update on this?

John

|||

Jaydog,

I would also be interested in finding out how that went.

JBW

can only set up snapshot & merge replication

Hi ,
I found that i could only set up a db in the server as either a
snapshot/merger replication with the transactional replication greyed out
any reason why i am not able to make it a transactional replication ?
tks & rdgs
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...ation/200512/1
are you running msde?
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
"maxzsim via droptable.com" <u14644@.uwe> wrote in message
news:587958988abb4@.uwe...
> Hi ,
> I found that i could only set up a db in the server as either a
> snapshot/merger replication with the transactional replication greyed out
>
> any reason why i am not able to make it a transactional replication ?
> tks & rdgs
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...ation/200512/1
|||... or personal edition?
Paul Ibison
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23lC3Vey%23FHA.3068@.TK2MSFTNGP09.phx.gbl...
> are you running msde?
> --
> 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
> "maxzsim via droptable.com" <u14644@.uwe> wrote in message
> news:587958988abb4@.uwe...
>
|||Hi ,
i am running sql server 2000 standard edition
rdgs
Paul Ibison wrote:[vbcol=seagreen]
>... or personal edition?
>Paul Ibison
>[quoted text clipped - 6 lines]
Message posted via http://www.droptable.com
|||Is there an error when you run this:
sp_dboption @.dbname = 'database'
, @.optname = 'published'
, @.optvalue = 'true'
Or are you possibly referring to the articles being greyed out (this is
because of a lack of a Primary key).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi Paul,
there's no error and i got "Published" returned
tks & rdgs
Paul Ibison wrote:
>Is there an error when you run this:
>sp_dboption @.dbname = 'database'
> , @.optname = 'published'
> , @.optvalue = 'true'
>Or are you possibly referring to the articles being greyed out (this is
>because of a lack of a Primary key).
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
>http://www.nwsu.com/0974973602p.html)
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...ation/200512/1
|||Please can you run the following code in your database. All you need to do
is a find and replace - change Region to a table name that has a PK. If
there are any messages, please post them back.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
-- Adding the transactional publication
exec sp_addpublication @.publication = N'TestPublication', @.restricted =
N'false', @.sync_method = N'native', @.repl_freq = N'continuous', @.description
= 'test', @.status = N'active', @.allow_push = N'true', @.allow_pull = N'true',
@.allow_anonymous = N'false', @.enabled_for_internet = N'false',
@.independent_agent = N'false', @.immediate_sync = N'false', @.allow_sync_tran
= N'false', @.autogen_sync_procs = N'false', @.retention = 336,
@.allow_queued_tran = N'false', @.snapshot_in_defaultfolder = N'true',
@.compress_snapshot = N'false', @.ftp_port = 21, @.ftp_login = N'anonymous',
@.allow_dts = N'false', @.allow_subscription_copy = N'false',
@.add_to_active_directory = N'false', @.logreader_job_name = N'TestPI-4'
exec sp_addpublication_snapshot @.publication =
N'TestPublication',@.frequency_type = 4, @.frequency_interval = 1,
@.frequency_relative_interval = 0, @.frequency_recurrence_factor = 1,
@.frequency_subday = 1, @.frequency_subday_interval = 0, @.active_start_date =
0, @.active_end_date = 0, @.active_start_time_of_day = 230000,
@.active_end_time_of_day = 0, @.snapshot_job_name =
N'TestPI-TestPublication-11'
GO
exec sp_grant_publication_access @.publication = N'TestPublication', @.login =
N'BUILTIN\Administrators'
GO
exec sp_grant_publication_access @.publication = N'TestPublication', @.login =
N'distributor_admin'
GO
exec sp_grant_publication_access @.publication = N'TestPublication', @.login =
N'sa'
GO
-- Adding the transactional articles
exec sp_addarticle @.publication = N'TestPublication', @.article = N'Region',
@.source_owner = N'dbo', @.source_object = N'Region', @.destination_table =
N'Region', @.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_Region', @.del_cmd = N'CALL sp_MSdel_Region', @.upd_cmd = N'MCALL
sp_MSupd_Region', @.filter = null, @.sync_object = null, @.auto_identity_range
= N'false'
GO
|||Hi Paul , when i ran ur script against the db that i want to create the
publication i got the following.
i am not sure abt the part that this edition does not support because i am
using the standard edition or how can i check the edition of my SQL Server ?
could be service pack issue ?
================================================== =====
Server: Msg 21108, Level 16, State 1, Procedure sp_addpublication, Line 275
This edition of SQL Server does not support transactional publications.
Server: Msg 15001, Level 11, State 1, Procedure sp_addpublication_snapshot,
Line 117
Object 'TestPublication' does not exist or is not a valid object for this
operation.
Server: Msg 20026, Level 16, State 1, Procedure sp_MSpublication_access, Line
42
The publication 'TestPublication' does not exist.
Server: Msg 20026, Level 16, State 1, Procedure sp_MSpublication_access, Line
42
The publication 'TestPublication' does not exist.
Server: Msg 20026, Level 16, State 1, Procedure sp_MSpublication_access, Line
42
The publication 'TestPublication' does not exist.
Server: Msg 14027, Level 11, State 1, Procedure sp_addarticle, Line 478
TestPublication does not exist in the current database.
================================================== =====
tks & rdgs
Paul Ibison wrote:
>Please can you run the following code in your database. All you need to do
>is a find and replace - change Region to a table name that has a PK. If
>there are any messages, please post them back.
>Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
>http://www.nwsu.com/0974973602p.html)
>-- Adding the transactional publication
>exec sp_addpublication @.publication = N'TestPublication', @.restricted =
>N'false', @.sync_method = N'native', @.repl_freq = N'continuous', @.description
>= 'test', @.status = N'active', @.allow_push = N'true', @.allow_pull = N'true',
>@.allow_anonymous = N'false', @.enabled_for_internet = N'false',
>@.independent_agent = N'false', @.immediate_sync = N'false', @.allow_sync_tran
>= N'false', @.autogen_sync_procs = N'false', @.retention = 336,
>@.allow_queued_tran = N'false', @.snapshot_in_defaultfolder = N'true',
>@.compress_snapshot = N'false', @.ftp_port = 21, @.ftp_login = N'anonymous',
>@.allow_dts = N'false', @.allow_subscription_copy = N'false',
>@.add_to_active_directory = N'false', @.logreader_job_name = N'TestPI-4'
>exec sp_addpublication_snapshot @.publication =
>N'TestPublication',@.frequency_type = 4, @.frequency_interval = 1,
>@.frequency_relative_interval = 0, @.frequency_recurrence_factor = 1,
>@.frequency_subday = 1, @.frequency_subday_interval = 0, @.active_start_date =
>0, @.active_end_date = 0, @.active_start_time_of_day = 230000,
>@.active_end_time_of_day = 0, @.snapshot_job_name =
>N'TestPI-TestPublication-11'
>GO
>exec sp_grant_publication_access @.publication = N'TestPublication', @.login =
>N'BUILTIN\Administrators'
>GO
>exec sp_grant_publication_access @.publication = N'TestPublication', @.login =
>N'distributor_admin'
>GO
>exec sp_grant_publication_access @.publication = N'TestPublication', @.login =
>N'sa'
>GO
>-- Adding the transactional articles
>exec sp_addarticle @.publication = N'TestPublication', @.article = N'Region',
>@.source_owner = N'dbo', @.source_object = N'Region', @.destination_table =
>N'Region', @.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_Region', @.del_cmd = N'CALL sp_MSdel_Region', @.upd_cmd = N'MCALL
>sp_MSupd_Region', @.filter = null, @.sync_object = null, @.auto_identity_range
>= N'false'
>GO
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...ation/200512/1
|||Hi
i am not too sure where to check the edition of the SQL server but below is
the version of the SQL from "SELECT @.@.version"
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
tks & rdgs
maxzsim wrote:[vbcol=seagreen]
>Hi Paul , when i ran ur script against the db that i want to create the
>publication i got the following.
>i am not sure abt the part that this edition does not support because i am
>using the standard edition or how can i check the edition of my SQL Server ?
>could be service pack issue ?
>================================================= ======
>Server: Msg 21108, Level 16, State 1, Procedure sp_addpublication, Line 275
>This edition of SQL Server does not support transactional publications.
>Server: Msg 15001, Level 11, State 1, Procedure sp_addpublication_snapshot,
>Line 117
>Object 'TestPublication' does not exist or is not a valid object for this
>operation.
>Server: Msg 20026, Level 16, State 1, Procedure sp_MSpublication_access, Line
>42
>The publication 'TestPublication' does not exist.
>Server: Msg 20026, Level 16, State 1, Procedure sp_MSpublication_access, Line
>42
>The publication 'TestPublication' does not exist.
>Server: Msg 20026, Level 16, State 1, Procedure sp_MSpublication_access, Line
>42
>The publication 'TestPublication' does not exist.
>Server: Msg 14027, Level 11, State 1, Procedure sp_addarticle, Line 478
>TestPublication does not exist in the current database.
>================================================= ======
>tks & rdgs
>[quoted text clipped - 45 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...ation/200512/1
|||You're using MSDE (not 'Standard').
You'll need to change edition of SQL Server.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)