Replication to SQL Server 2005 Express

Hello.
I have a SQL Server 2005 Enterprise Edition with a database. I want to make
a merge replication of that database to some machines with SQL Server 2005
Express Edition's installed. I have created a merge replication publishment
and if I make a local subscription on the SQL Server 2005 Enterprise Edition
everything works great. But if I make a subscription on a SQL Server 2005
Express Edition which is in the same network with the publisher, the
databases do not synchronize (if I make a pull subscription I have an
'Uninitialized subscripition' warning in the Replication Monitor and if I
make a push subscription the status is 'Synchronizing' but my data is not
replicated).
I tried to do things like enabling remote access to the SQL Express server
and disabling the firewall on that machine, but it still doesn't work. What
should I do?
Thank you in advance,
Stefan Filip
Run profiler on the subscriber/express machine to find out where it is
getting stuck.
http://www.zetainteractive.com - Shift Happens!
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
"Stefan Filip" <StefanFilip@.discussions.microsoft.com> wrote in message
news:2BA863F6-637D-4D0D-8AB2-8FB97EE8AD59@.microsoft.com...
> Hello.
> I have a SQL Server 2005 Enterprise Edition with a database. I want to
> make
> a merge replication of that database to some machines with SQL Server 2005
> Express Edition's installed. I have created a merge replication
> publishment
> and if I make a local subscription on the SQL Server 2005 Enterprise
> Edition
> everything works great. But if I make a subscription on a SQL Server 2005
> Express Edition which is in the same network with the publisher, the
> databases do not synchronize (if I make a pull subscription I have an
> 'Uninitialized subscripition' warning in the Replication Monitor and if I
> make a push subscription the status is 'Synchronizing' but my data is not
> replicated).
> I tried to do things like enabling remote access to the SQL Express server
> and disabling the firewall on that machine, but it still doesn't work.
> What
> should I do?
> Thank you in advance,
> Stefan Filip

Replication Standard or Enterprise

In setting up replication between databases do both sql installations have to be enterprise or can it be done with both sql server standard edition.
thanks,Replication is included in Standard Edition.|||Is there a difference in using enterprise... or standard in regards to replication... I can not find much information stating the difference in choosing an edition...
here @. work ... the prod server they want to replicate has already been built using standard... but other... admins... say it would have to be enterprise...|||Is there a difference in using enterprise... or standard in regards to replication... I can not find much information stating the difference in choosing an edition...
here @. work ... the prod server they want to replicate has already been built using standard... but other... admins... say it would have to be enterprise...

Tell the other ...admins ... to take a hike:


SQL Server 2000 Standard Edition

This is a more affordable option for small-sized and medium-sized organizations that do not require the advanced scalability, availability, performance, or analysis features of SQL Server 2000 Enterprise Edition. Standard Edition can be used on symmetric multiprocessing systems with up to 4 CPUs and 2 GB of RAM.
Standard Edition includes the core functionality needed for non-mission-critical e-commerce, data warehousing, and line-of-business solutions. For instance, all of the XML features present in Enterprise Edition are also included in Standard Edition. And while a handful of advanced OLAP features are reserved for Enterprise Edition, all data mining features and the core OLAP functionality are included in SQL Server 2000 Analysis Services in Standard Edition. Similarly, components that other database vendors charge for as separate add-on products for their highest-end editions are included in Standard Edition:
Data Transformation Services (DTS)
Replication (snapshot, transactional, and merge)
Full-Text Search
English Query
Stored procedure development and debugging tools
SQL Profiling and performance analysis tools
Before choosing Standard Edition, make sure you review "Features Supported by the Editions of SQL Server 2000" in SQL Server Books Online.|||Kindly ask the "other admins" for proof of this. Perhaps, if you build the replication into the QA system (a good idea, anyway), you can prove to them it is possible.|||I appreciate the feedback... and will do a lot more research... any experienced suggestions or tips that a tutorial or book might not mention .... thanks again guys...|||Or maybe they would like to read the 2005 features for themselves:

http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx|||I have a solution that not only replicates the data (standard or enterprise, 2000 or 2005) but also load balances read-only statements and provides effective means of resynchronization. I work for a company, PCTI (Parallel Computers Technology Inc), out of the Philadelphia area. We have a product, DBx, that does Parallel Synchronous Real Time Replication (up to 16 servers, local or remote) guaranteeing zero-loss of transactions. Anyone looking for more information should visit http://www.pcticorp.com or send me a private message via dbforums.com.

Replication question

Using the "Pull New Subscription" wizrd in the enterprise manager, I can
create a subscription without a problem.
Howwever using TSQL I cannot do the same thing:
Using this sequence:
sp_addSubscription (on publisher)
sp_addPullSubscription (on subscriber)
sp_addPullSubscription_Agent (on subscriber)
The error I get is:
the "Subscription is not active"
Any hints on what I'm doing wrong will be most appreciated
when you created your publication you have to set @.status='active'
to check to see if you forgot to do this, expand your database, right click
on your publication and see if the push new susbcription menu option is
enabled.
If it is disabled do this
sp_changepublication 'publicationname','status','active'
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Ernesto" <mathematicus@.yahoo.com> wrote in message
news:4v2dnTB4KNHDF4bcRVn-jw@.speakeasy.net...
> Using the "Pull New Subscription" wizrd in the enterprise manager, I can
> create a subscription without a problem.
> Howwever using TSQL I cannot do the same thing:
> Using this sequence:
> sp_addSubscription (on publisher)
> sp_addPullSubscription (on subscriber)
> sp_addPullSubscription_Agent (on subscriber)
> The error I get is:
> the "Subscription is not active"
> Any hints on what I'm doing wrong will be most appreciated
>
>
|||As I check the status is saya that it is active. yet I still get the error
when doing things via VB code/
Is there any kind of detail I can provide that may halp figure this out?
Thanks for your help
ps too bad your book is not available now!
|||what is the error number you are getting?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Ernesto" <mathematicus@.yahoo.com> wrote in message
news:4bOdnd3Jr_C8e4bcRVn-pA@.speakeasy.net...
> As I check the status is saya that it is active. yet I still get the error
> when doing things via VB code/
> Is there any kind of detail I can provide that may halp figure this out?
> Thanks for your help
> ps too bad your book is not available now!
>

Replication Pull subscription problem

Iam trying to pull subscription and Iam getting same error over and over again. The error says:
****SQL Server Enterprise Merger could not create a pull subscription to publication "database name"
Error 15004: Name cannot be null *****
ThanksHi

Its because of non-existence or invalid server info on sysservers table. Please follow the instructions to fix the above problem.

exec sp_dropserver <your_local_server_name> -- subscriber

exec sp_dropserver <remote_server_name> -- publisher

exec sp_addserver <your_local_server_name>,local

exec sp_addserver <remote_server_name>

shutdown -- it is mandatory to take effect otherwise you still get the same error
go

Start the sql server with SQLSERVERAGENT

exec sp_helpserver -- it should display your local server and publisher

Then, try configure pull subscription

Cheers
Sekar|||What version does this happen in? I thought Microsoft fixed this problem a while ago.

Replication problem

I am trying to set up a pull subscription replication using SQL Server
Enterprise Manager. I get an error stating:
....It cannot create named subscription because the publication does not
allow named pull subscription...
How do I enable the named pull subscription on the publisher?
Thanks in advance.Hi Antonin,
You may have to enable Pull Subscription and Anonymous Subscription for the
Publication.
You may achieve this by
1. Click on Tools -> Replication -> Create and Manage Publication.
2. Expand the Published Database and select the publication name.
3. Click on Properties and Subscription
4. In the Publication Properties Dialog Box
5. Switch to Subscription Option tab
6. In this tab you will find two checkboxes under "Subscription Creation"
option,
"Allow Pull Subscription"
"Allow Anonymous Subscription"
Please tick both the check boxes to allow Pull Anonymous Subscription
for that publication.
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Ashish,
Thanks for your reply. I followed your instructions and it worked OK.
However, there is Last Action on the publisher " A snapshot was not
generated because no subscription needed initialization.
Antonin
"Ashish Ruparel [MSFT]" <v-ashrup@.online.microsoft.com> wrote in message
news:TeZcQaXOEHA.1016@.cpmsftngxa10.phx.gbl...
> Hi Antonin,
> You may have to enable Pull Subscription and Anonymous Subscription for
the
> Publication.
> You may achieve this by
> 1. Click on Tools -> Replication -> Create and Manage Publication.
> 2. Expand the Published Database and select the publication name.
> 3. Click on Properties and Subscription
> 4. In the Publication Properties Dialog Box
> 5. Switch to Subscription Option tab
> 6. In this tab you will find two checkboxes under "Subscription Creation"
> option,
> "Allow Pull Subscription"
> "Allow Anonymous Subscription"
> Please tick both the check boxes to allow Pull Anonymous Subscription
> for that publication.
>
> HTH
> Ashish
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>

Replication Monitor

experiencing some very odd behavior in Enterprise Manager.
I have a process that performs the following:
1.) Restores a published database from Server A onto Server B. The
databases
are identical and they are both published.
2.) I run a script that then deletes the subscriptions to the
publication on
Server B. I do this via SP_DROPSUBSCRIPTION.
3.) I run a script that then deletes the publication. I do this via
SP_DROPPUBLICATION.
4.) Deletes the distribution database.
5.) Deletes the old jobs.
6.) Creates the publication from pregenerated scripts.
7.) Adds the subscriber.
8.) Adds the subscription.
9.) Generates the snapshot and applies it.
What's happening is that I'm seeing the job name that's assigned to the
distribution job increment by 1 each time this process is run. Also,
I'm seeing ten instances of the publication showing up in the tree view.
When I look in SYSPUBLICATIONS, there is only ONE row!!! Shouldn't
Replication Monitor clean itself up?
Everything appears to be rtunning just fine, transactions being
replicated, etc. I'm just wondering is there something I'm missing in my
steps.
Plus, after two or three months of this, might not look so good having 90
publications showing up in the tree view.
Thanks!
first off run a sp_MSload_replication_status. This can occasionally correct
these problems. Secondly, it looks like your replication metadata is messed
up. It is normal for the publications to increment their names with every
new publication. However, to determine how to fix your error I need to know
which node you are getting the error in?
The Publication node in the replication folder? The Publishers node in the
Replication Monitor folder?
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
"A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
news:FE4B9FD8-5948-45AF-A3F8-8F9867CFBC23@.microsoft.com...
> experiencing some very odd behavior in Enterprise Manager.
>
> I have a process that performs the following:
>
> 1.) Restores a published database from Server A onto Server B. The
> databases
> are identical and they are both published.
> 2.) I run a script that then deletes the subscriptions to the
> publication on
> Server B. I do this via SP_DROPSUBSCRIPTION.
> 3.) I run a script that then deletes the publication. I do this via
> SP_DROPPUBLICATION.
> 4.) Deletes the distribution database.
> 5.) Deletes the old jobs.
> 6.) Creates the publication from pregenerated scripts.
> 7.) Adds the subscriber.
> 8.) Adds the subscription.
> 9.) Generates the snapshot and applies it.
>
> What's happening is that I'm seeing the job name that's assigned to the
> distribution job increment by 1 each time this process is run. Also,
> I'm seeing ten instances of the publication showing up in the tree view.
> When I look in SYSPUBLICATIONS, there is only ONE row!!! Shouldn't
> Replication Monitor clean itself up?
> Everything appears to be rtunning just fine, transactions being
> replicated, etc. I'm just wondering is there something I'm missing in my
> steps.
> Plus, after two or three months of this, might not look so good having 90
> publications showing up in the tree view.
>
> Thanks!
>
>
|||Hilary:
I'm seeing this in the publishers node under Replication Monitor...
When would I run the sp_MSload_Replication_Status? I just ran it and it
killed my replication. I'm guessing you don't want to run that proc after
replication has been established...
Thanks!
"Hilary Cotter" wrote:

> first off run a sp_MSload_replication_status. This can occasionally correct
> these problems. Secondly, it looks like your replication metadata is messed
> up. It is normal for the publications to increment their names with every
> new publication. However, to determine how to fix your error I need to know
> which node you are getting the error in?
> The Publication node in the replication folder? The Publishers node in the
> Replication Monitor folder?
> --
> 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
> "A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
> news:FE4B9FD8-5948-45AF-A3F8-8F9867CFBC23@.microsoft.com...
>
>
|||What do you mean by it "killed" off replication? I should fix transient
errors. Are you saying that some agents are no longer showing up in the
snapshot/distribution/log reader agent folders?
If so, I think this is caused by scripting out replication and running the
same script in a different database without modifying the snapshot, log
reader, or distribution agent names, and without modifying the publication
name. I think you will find that the agents just don't show up, but
everything works fine.
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
"A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
news:B69FA4F3-EFA7-40B2-A709-9B08335CE455@.microsoft.com...[vbcol=seagreen]
> Hilary:
> I'm seeing this in the publishers node under Replication Monitor...
> When would I run the sp_MSload_Replication_Status? I just ran it and it
> killed my replication. I'm guessing you don't want to run that proc after
> replication has been established...
> Thanks!
> "Hilary Cotter" wrote:
correct[vbcol=seagreen]
messed[vbcol=seagreen]
every[vbcol=seagreen]
know[vbcol=seagreen]
the[vbcol=seagreen]
the[vbcol=seagreen]
view.[vbcol=seagreen]
my[vbcol=seagreen]
90[vbcol=seagreen]
|||I stand corrected...everything came back.
But I'm still seeing the multiple publications under the publishers tab of
the replication monitor...
"Hilary Cotter" wrote:

> What do you mean by it "killed" off replication? I should fix transient
> errors. Are you saying that some agents are no longer showing up in the
> snapshot/distribution/log reader agent folders?
> If so, I think this is caused by scripting out replication and running the
> same script in a different database without modifying the snapshot, log
> reader, or distribution agent names, and without modifying the publication
> name. I think you will find that the agents just don't show up, but
> everything works fine.
> --
> 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
> "A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
> news:B69FA4F3-EFA7-40B2-A709-9B08335CE455@.microsoft.com...
> correct
> messed
> every
> know
> the
> the
> view.
> my
> 90
>
>
|||...also, the scripts that are being used to recreate the replication topology
were generated on the Server B - so the agent names, databases, subscription
names are all correct for that particular server...
"A. Robinson" wrote:
[vbcol=seagreen]
> I stand corrected...everything came back.
> But I'm still seeing the multiple publications under the publishers tab of
> the replication monitor...
> "Hilary Cotter" wrote:

Replication Monitor

I'm experiencing some very odd behavior in Enterprise Manager.

I have a process that performs the following:

1.) Restores a published database from Server A onto Server B. The
databases
are identical and they are both published.
2.) I run a script that then deletes the subscriptions to the
publication on
Server B. I do this via SP_DROPSUBSCRIPTION.
3.) I run a script that then deletes the publication. I do this via
SP_DROPPUBLICATION.
4.) Deletes the distribution database.
5.) Deletes the old jobs.
6.) Creates the publication from pregenerated scripts.
7.) Adds the subscriber.
8.) Adds the subscription.
9.) Generates the snapshot and applies it.

What's happening is that I'm seeing the job name that's assigned to the

distribution job increment by 1 each time this process is run. Also,
I'm
seeing ten instances of the publication showing up in the tree view.

Everything appears to be rtunning just fine, transactions being
replicated,
etc. I'm just wondering is there something I'm missing in my steps.
Plus,
after two or three months of this, might not look so good having 90
publications showing up in the tree view.

Thanks!You might get a better response in
microsoft.public.sqlserver.replication

Simon

Replication issues with MSDE and SQL Server Enterprise

Hello--
I'm am having difficulty setting up what I thought would
be something relatively simple to accomplish. I have two
client computers running XP, each using a local copy of
MSDE2000 to store data. I also have a server running
Windows 2000 AS and SQL Server Enterprise.
What I'm trying to do is have the data that's logged on
the client computers replicate to the server. I have run
into a variety of issues, most seem to be related to
security problems. I have all SQL Server instances set up
to use TCP/IP and named pipes, and all set for mixed mode
authentication. I am not using the server as a domain
controller, but I have created matching user accouts with
administrator priviliges on each of the three computers in
question.
When I create a publication on one of the two client
computers, sometimes a snaphot is generated immediately,
sometimes it isn't. When I try to create a pull
subscription on the server, I typically get an error about
being unable to connect to the distributor (I presume
security-releated problems).
I feel as if I'm missing something obvious, because this
seem like a very straightforward setup. What am I doing
wrong?
Thanks in advance for any help.
Chris Langston
exactly how are you connecting to your Publisher? ActiveX, SQM DMO?
If you are using ActiveX controls you have to define the network method you
are using to connect to your publisher/distributor by using
PublisherAddress/PublisherNetwork and DistributorAddress/DistributorNetwork.
If you are pulling a subscription using UNC you will have to ensure that the
SQL Server agent account on the subscriber has rights to the network share
on the publisher. The easiest way to do this is to make sure that the SQL
Server agent account the subscribers run under is the same one that it runs
under on the Publisher and this account is in the local admin group. If you
can't make them the same domain account, give them the same name and
password.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Chris Langston" <clangst@.vectorcorporation.com> wrote in message
news:512901c4807f$6260a7c0$a401280a@.phx.gbl...
> Hello--
> I'm am having difficulty setting up what I thought would
> be something relatively simple to accomplish. I have two
> client computers running XP, each using a local copy of
> MSDE2000 to store data. I also have a server running
> Windows 2000 AS and SQL Server Enterprise.
> What I'm trying to do is have the data that's logged on
> the client computers replicate to the server. I have run
> into a variety of issues, most seem to be related to
> security problems. I have all SQL Server instances set up
> to use TCP/IP and named pipes, and all set for mixed mode
> authentication. I am not using the server as a domain
> controller, but I have created matching user accouts with
> administrator priviliges on each of the three computers in
> question.
> When I create a publication on one of the two client
> computers, sometimes a snaphot is generated immediately,
> sometimes it isn't. When I try to create a pull
> subscription on the server, I typically get an error about
> being unable to connect to the distributor (I presume
> security-releated problems).
> I feel as if I'm missing something obvious, because this
> seem like a very straightforward setup. What am I doing
> wrong?
> Thanks in advance for any help.
> Chris Langston
>
>