Ok we are finally get close to testing SQL 2005 with SQL Express 2005:). So I have a publication named hh3_100_pub. We currently ghost each unit so the instance name and database names are the same. My question is we have 20 possible subcribers. Does each subsriber need to:
1. Have a different instance name?
2. Have a different database name?
What would I do to add another subscriber with the same instance name and
database name?
code below
--BEGIN: Script to be run at Publisher
'B-DB\BDBSERVER'--
use [sandiego] --database to set as publication
exec sp_addmergesubscription @.publication = N'hh3_100_pub', --the name given
to the publication during the creation of the publication via the wizard
@.subscriber = N'vm2ksqlexpress\hh3', --name of the subscriber client
instance
@.subscriber_db = N'wip', --name of the subscriber db
@.subscription_type = N'pull',
@.subscriber_type = N'global',
@.subscription_priority = 0,
@.sync_type = N'Automatic'
GO
--BEGIN: Script to be run at Subscriber
'vm2ksqlexpress\hh3'--
use [wip]
exec sp_addmergepullsubscription
@.publisher = N'B-DB\BDBSERVER',
@.publication = N'hh3_100_pub',
@.publisher_db = N'sandiego',
@.subscriber_type = N'Local',
@.subscription_priority = 0,
@.description = N'',
@.sync_type = N'Automatic'
Posting the response from another thread:
-->
A subscription needs to be on a database on a server.
So on a server, you can have multiple databases and each of these databases
can have subscriptions from a publication.
If you have multiple servers/instances, you can have the same named database
on each of them and then each such database can have a subscription from a
publication
Since you cannot have mutiple databases of the same name, you cannot have
subscription.
Either you will have to use different database names on the same server or
different servers/instances with same database names.
No comments:
Post a Comment