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 Sync on Windows Vista

On windows XP there is a Synchronize program in Accessories. When I run our replication scripts on a SQL Server Express on the XP machine and start the Synchronize program there are items there that allow me to replicate as well as set a schedule, etc.

On Windows Vista there is a Sync Center, but replication doesn't show up here.

I've searched high and low on Google and am not coming up with anything useful, which leads me to believe this is something very simple that I'm overlooking...

Does anyone know how to make your replication show up on the Sync Center in vista, or is there another application that I should download?

Thanks,

Brian

I could be wrong, but I do not believe those are the same. I think Sync Manager in Vista is a built-in tool for synchronizing PDA's and thing like that. However, so I do not mis-speak, I am testing that now because we are also at the point of testing synchronization with Vista.

I will let you know what i find.

Scott

|||To add files to Sync Center, on the (Vista) machine you want to have the offline copy on, open explorer and navigate to the network share the original file or directory is on. Right-click and on the context menu select "Always Available Online." The SyncCenter icon will be superimposed on the icon to show it is being copied.

Replication Sync on Windows Vista

On windows XP there is a Synchronize program in Accessories. When I run our replication scripts on a SQL Server Express on the XP machine and start the Synchronize program there are items there that allow me to replicate as well as set a schedule, etc.

On Windows Vista there is a Sync Center, but replication doesn't show up here.

I've searched high and low on Google and am not coming up with anything useful, which leads me to believe this is something very simple that I'm overlooking...

Does anyone know how to make your replication show up on the Sync Center in vista, or is there another application that I should download?

Thanks,

Brian

I could be wrong, but I do not believe those are the same. I think Sync Manager in Vista is a built-in tool for synchronizing PDA's and thing like that. However, so I do not mis-speak, I am testing that now because we are also at the point of testing synchronization with Vista.

I will let you know what i find.

Scott

|||To add files to Sync Center, on the (Vista) machine you want to have the offline copy on, open explorer and navigate to the network share the original file or directory is on. Right-click and on the context menu select "Always Available Online." The SyncCenter icon will be superimposed on the icon to show it is being copied.

Replication SQL Server 2005 <-> SQL Server 2005 Express

Hi,
I'm Roby Eisenbraun Martins. I'm a C++, VB, C# developer.
I'm developing a new application that requires work off-line from the
database.
I'm trying to work with SQL server 2005 replication, copying the data to
a SQL Express database ( .mdf ), work off-line and then merge back into the
publisher database.
But It is not working.
Where can I find more articles about it?
Thank you,
Roby Eisenbraun Martins
What error message are you getting? There is no SQL Server Agent with SQL
Server Express. You have to run your sync through windows synchronization
manager or at scheduler (Task Scheduler).
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
"Roby Eisenbraun Martins" <RobyEisenbraunMartins@.discussions.microsoft.com >
wrote in message news:E6A10EA2-CEAE-4DB0-943D-99B76D287CE4@.microsoft.com...
> Hi,
> I'm Roby Eisenbraun Martins. I'm a C++, VB, C# developer.
> I'm developing a new application that requires work off-line from the
> database.
> I'm trying to work with SQL server 2005 replication, copying the data
> to
> a SQL Express database ( .mdf ), work off-line and then merge back into
> the
> publisher database.
> But It is not working.
> Where can I find more articles about it?
> Thank you,
> Roby Eisenbraun Martins
>
|||Hi Hilary,
Thank you for your help.
I can create the publication but when I try to create a subscriber for
that publication from a SQL Express database It doesn't work. It returns with
an error message "Cannot find Server".
I tried creating the subscriber using the SQL Management studio but I
cann't select the SQLEXPRESS server as a subscriber.
How can I make a .mdf file as a subscriber for my publication?
Thank you,
Roby Eisenbraun Martins
"Hilary Cotter" wrote:

> What error message are you getting? There is no SQL Server Agent with SQL
> Server Express. You have to run your sync through windows synchronization
> manager or at scheduler (Task Scheduler).
> --
> 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
> "Roby Eisenbraun Martins" <RobyEisenbraunMartins@.discussions.microsoft.com >
> wrote in message news:E6A10EA2-CEAE-4DB0-943D-99B76D287CE4@.microsoft.com...
>
>
|||Here are a couple more items to check while trying to get your connectivity
to the remote SQL Express installation working...
By default SQL Server 2005 Express SKU will install with network protocols
disabled. If you want to use a tool external to your SQL Express
installation box to connect to it, then you need to enable the network
protocols. In the "SQL Server 2005" program folder from the start menu, you
should be able to find a "Configuration Tools" folder. In this folder launch
the "SQL Server Surface Area Configuration" tool. After connecting to the
SQL Express instance in the tool, look under "Database Services" and
configure the "Remote Connections option.
Another item to note is that by default in SQL Server 2005 Express SKU, the
default instance is SQLEXPRESS, not MSSQLSERVER. When you try to connect
remotely, you need to use the server name and instance name, i.e.
<ComputerName>\SQLEXPRESS
Tom
This posting is provided "AS IS" with no warranties, and confers no rights.
"Roby Eisenbraun Martins" wrote:
[vbcol=seagreen]
> Hi Hilary,
> Thank you for your help.
> I can create the publication but when I try to create a subscriber for
> that publication from a SQL Express database It doesn't work. It returns with
> an error message "Cannot find Server".
> I tried creating the subscriber using the SQL Management studio but I
> cann't select the SQLEXPRESS server as a subscriber.
> How can I make a .mdf file as a subscriber for my publication?
> Thank you,
> Roby Eisenbraun Martins
> "Hilary Cotter" wrote:

replication question

can replication between sql server 2005 standard edition and express editionSQL Server 2005 Express can only act as the subscriber in a replication
process.
ML
http://milambda.blogspot.com/|||I think it's also the case that it can only subscribe to an sql 2005
publisher, is this right?|||Although this is not quite obvious from the following article, I think SQL
Server 2005 Express can act as a subscriber in a SQL 2000 replication (where
either the Publisher or the Distributer are SQL Sever 2000).
http://msdn2.microsoft.com/en-us/library/ms143699(SQL.90).aspx
I'm not certain.
ML
http://milambda.blogspot.com/|||aahh - I see it depends on the type of replication.
transactional it's fine:
"A read-only Subscriber to a transactional publication can be any
version within two versions of the Publisher version. For example: a
SQL Server version 7.0 Publisher running can have SQL Server 2005
Subscribers; and a SQL Server 2005 Publisher can have SQL Server
version 7.0 Subscribers."
but merge it isn't
"A Subscriber to a merge publication can be any version less than or
equal to the Publisher version."
thanks for the link

Replication of structure

Hello

I have a server with SQL Server 2005 and several machines with SQL Server Express.

I have my "master" DB on the SQL Server 2005 on which I have created a transactional publication (push)

Then all my other DB have a subscription to that publication.

I have different scenarios:

The structure needs to be replicated --> OK it works The data of some table needs to be replicated --> OK it works Whatever the data at the client, they are replaced after the replication The data of some table needs to be partially replicated --> OK it works Whatever the data at the client, they are replaced after the replication (only part of the server data is replicated with the filters) Some data must not be replicated --> Don't know how to do this Whatever the data at the client and at the server, I want them unchanged after the replication

Can you help me with this latest point ? I have tried with the filtering but it always remove all data from the client. What I need is: If I have 10 lines on my server, and 20 on my client, I only want the structure to be updated. But I still need my 10 lines on the server and my 20 on my client after the replication.

Thanks !

By default, when you apply the snapshot, it will drop the table(s) at the subscriber and replace it with refreshed data generated by the snapshot. If you don't want the data dropped, then make sure to clear the "initialize" checkbox in the subscription wizard. See topic "How to: Initialize a Subscription Manually".

Replication is renaming my Stored Procedures on Client only

I am new to replication but I have a question, I have my server which is using a transaction replication process and a client with using SQL Express with replication turned on. I have the identical DB on both nodes yet when I subsrcibe to the server from the client, data is transfer but for some reason, all of my stored procedures are renamed with sp_MSDel_DBOxxxx. How do I keep SQL from renaming these SP's? The server maintains the origial names to the SPs its just happening on my client.

Thanks

You can customize the names of these stored procs in the article properties.|||

If I understand correctly, the SPs you're seeing on client db are not the renamed copy of your original sps, those sp_MSDel_DBOxxxx sps are created and used exclusively by replication, they should not affect your existing sps in anyway. However, if you want to control how those replication sps are named you can use the approach Greg suggested.

Thanks,

Zhiqiang Feng

|||

My Server SP's are named properly, for example usp_AddActivityLog is the proper name of my custom SP. After replication occurs the name of the same SP on my client is now named sp_MSdel_dboActivityLog.

In the Article Property <Default is based on stored procedure name> is in the destination object name. And here is the code for SP:

set ANSI_NULLS ON

set QUOTED_IDENTIFIER ON

go

ALTER PROCEDURE [dbo].[usp_AddActivityLog]

@.activityLogID bigint,

@.agencyofficer_id bigint,

@.lookup_id int,

@.remarks varchar(200) = '',

@.caseLinkID bigint = null,

@.startTime dateTime = null,

@.endTime datetime = null,

@.location varchar(200) = '',

@.callForServiceID bigint = 0

AS

SET NOCOUNT ON

DECLARE @.ret int

IF (@.activityLogID <> 0)

BEGIN

UPDATE ActivityLog SET

EndTime = @.endTime,

fk_CaseLinkID = @.caseLinkID,

remarks = @.remarks,

location = @.location,

fk_CallForServiceID = @.callForServiceID

WHERE pk_activityID = @.activityLogID

SET @.ret = @.@.ERROR

IF @.ret <> 0

BEGIN

INSERT INTO ErrorLog VALUES ('Update of ActivityLog failed.', GetDate())

RETURN -1

END

ELSE

RETURN @.activityLogID

END

ELSE

BEGIN

INSERT INTO ActivityLog (fk_AgencyOfficersID, fk_ActivityLookupID, StartTime, EndTime,Remarks, fk_CaseLinkID, location, fk_CallForServiceID)

VALUES (@.agencyofficer_id, @.lookup_id, @.startTime, '', @.remarks, @.caseLinkID, @.location, @.callForServiceID)

SET @.ret = @.@.ERROR

IF @.ret <> 0

BEGIN

INSERT INTO ErrorLog VALUES ('Insert into ActivityLog failed.', GetDate())

RETURN -1

END

ELSE

RETURN @.@.identity

END

Any Idea why they are being renamed?

Thanks

|||

Distribution agent doesn't rename anything, it just applies what's in the snapshot folder. Look in your snapshot folder to see what stored procedures are being generated. If the proper names are there, then the procs you see must have previously existed. If the incorrect proc names are being generated, then you need to doublecheck the article properties to see what the problem could be.

I just tried your scenario on a SQL 2005 machine with different proc names, they were created properly at the subscriber. IF there's something else i missed, please let me know.