Merge Replication w/ Web Synchronization Across Non-Trusted Domain

I have a requirement to replicate a portion of a 2005 database using merge
replication where the database server is in a workgroup at location A and the
web server is in an AD domain at location B. Both locations are connected
via a VPN.
Becuase of the disparate domains we are unable to push snapshots to a share
on the Web Server w/o using FTP. After specifying the FTP information in the
FTP Snapshot and Internet dialog, the following message is returned when
attempting to start the Snapshot Agent:
Message: The replication agent failed to create the directory
'\\172.27.1.187\unc\ftp\DAYMONJPSV02$TEST_CORE_APP RISCORE1\20071218021362\'.
Stack: at
Microsoft.SqlServer.Replication.Utilities.CreateDi rectoryWithExtendedErrorInformation(String directory)
at
Microsoft.SqlServer.Replication.Snapshot.SnapshotP rovider.CreateSnapshotFolders()
at
Microsoft.SqlServer.Replication.Snapshot.MergeSnap shotProvider.CreateSnapshotFolders()
at
Microsoft.SqlServer.Replication.Snapshot.SqlServer SnapshotProvider.GenerateSnapshot()
at Microsoft.SqlServer.Replication.SnapshotGeneration Agent.InternalRun()
at Microsoft.SqlServer.Replication.AgentCore.Run() (Source: MSSQL_REPL,
Error number: MSSQL_REPL52026)
Get help: http://help/MSSQL_REPL52026
Source: mscorlib
Target Site: Void WinIOError(Int32, System.String)
Message: Message: Logon failure: unknown user name or bad password.
Stack: at System.IO.__Error.WinIOError(Int32 errorCode, String
maybeFullPath)
at System.IO.Directory.InternalCreateDirectory(String fullPath, String
path, DirectorySecurity dirSecurity)
at System.IO.Directory.CreateDirectory(String path, DirectorySecurity
directorySecurity)
at
Microsoft.SqlServer.Replication.Utilities.CreateDi rectoryWithExtendedErrorInformation(String directory) (Source: mscorlib, Error number: 0)
The user id and password are those of a domain user for the FTP server at
location B. Do I have to use a non-AD account?
You need to use a snapshot account which has rights to modify to
\\172.27.1.187\unc. You specify this account in sp_addpublication_snapshot
using the @.job_login and @.job_password parameters.
This account should exist on \\172.27.1.187 and your publisher.
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
"parchk" <parchk@.discussions.microsoft.com> wrote in message
news:7575E064-365A-49B4-B479-AD3C7D4E14C8@.microsoft.com...
>I have a requirement to replicate a portion of a 2005 database using merge
> replication where the database server is in a workgroup at location A and
> the
> web server is in an AD domain at location B. Both locations are connected
> via a VPN.
> Becuase of the disparate domains we are unable to push snapshots to a
> share
> on the Web Server w/o using FTP. After specifying the FTP information in
> the
> FTP Snapshot and Internet dialog, the following message is returned when
> attempting to start the Snapshot Agent:
> Message: The replication agent failed to create the directory
> '\\172.27.1.187\unc\ftp\DAYMONJPSV02$TEST_CORE_APP RISCORE1\20071218021362\'.
> Stack: at
> Microsoft.SqlServer.Replication.Utilities.CreateDi rectoryWithExtendedErrorInformation(String
> directory)
> at
> Microsoft.SqlServer.Replication.Snapshot.SnapshotP rovider.CreateSnapshotFolders()
> at
> Microsoft.SqlServer.Replication.Snapshot.MergeSnap shotProvider.CreateSnapshotFolders()
> at
> Microsoft.SqlServer.Replication.Snapshot.SqlServer SnapshotProvider.GenerateSnapshot()
> at Microsoft.SqlServer.Replication.SnapshotGeneration Agent.InternalRun()
> at Microsoft.SqlServer.Replication.AgentCore.Run() (Source: MSSQL_REPL,
> Error number: MSSQL_REPL52026)
> Get help: http://help/MSSQL_REPL52026
> Source: mscorlib
> Target Site: Void WinIOError(Int32, System.String)
> Message: Message: Logon failure: unknown user name or bad password.
> Stack: at System.IO.__Error.WinIOError(Int32 errorCode, String
> maybeFullPath)
> at System.IO.Directory.InternalCreateDirectory(String fullPath, String
> path, DirectorySecurity dirSecurity)
> at System.IO.Directory.CreateDirectory(String path, DirectorySecurity
> directorySecurity)
> at
> Microsoft.SqlServer.Replication.Utilities.CreateDi rectoryWithExtendedErrorInformation(String
> directory) (Source: mscorlib, Error number: 0)
> The user id and password are those of a domain user for the FTP server at
> location B. Do I have to use a non-AD account?
|||Thanks Hillary. I am assuming that becasue the servers are in two different
security domains that the account should be local on both servers? Also, if
the publication has already been created, can it be modified to modify the
job_login and job_password parameters? Thanks in advance.
"Hilary Cotter" wrote:

> You need to use a snapshot account which has rights to modify to
> \\172.27.1.187\unc. You specify this account in sp_addpublication_snapshot
> using the @.job_login and @.job_password parameters.
> This account should exist on \\172.27.1.187 and your publisher.
> --
> 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
> "parchk" <parchk@.discussions.microsoft.com> wrote in message
> news:7575E064-365A-49B4-B479-AD3C7D4E14C8@.microsoft.com...
>
>
|||Exactly, it should be a local account on both servers.
You can modify the snapshot account by right clicking on the publication in
SSMS, selecting properties and clicking on the agent security tab.
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
"parchk" <parchk@.discussions.microsoft.com> wrote in message
news:915C3515-3E0A-4755-88B7-DE72D927A0E2@.microsoft.com...[vbcol=seagreen]
> Thanks Hillary. I am assuming that becasue the servers are in two
> different
> security domains that the account should be local on both servers? Also,
> if
> the publication has already been created, can it be modified to modify the
> job_login and job_password parameters? Thanks in advance.
> "Hilary Cotter" wrote:

merge replication over internet

Hello!
I'm doing replication over non-trusted domains. I'm using FTP server to do
that.
I've also read Paul's articel about replication over non - trusted domains.
I'm using snapshot and merge replication.
Snapshot replication works OK, without any problems, but MERGE replication
gives me this error:
The schema script '' could not be propagated to the subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
------
The process could not connect to FTP site 'PC' using port 21.
(Source: STREZNIK\SAOP (Agent); Error number: 0)
------
Can you help me,
Uros
Uros,
this type of replication normally falls down due to
configuration/connectivity issues that have to be looked at individually.
Please try using an FTP tool to test transferring the snapshot files.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul!
Does MERGE replication need any different settings than snapshot. Because
snapshot over FTP works without any problems.
What are the most common settings that make troubles for MERGE via FTP?
Thanks.
"Paul Ibison" wrote:

> Uros,
> this type of replication normally falls down due to
> configuration/connectivity issues that have to be looked at individually.
> Please try using an FTP tool to test transferring the snapshot files.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Sorry to ask the obvious, but are your FTP settings done correctly on the
merge publication (inc folder paths).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Well, I've made it as for SNAPSHOT.
Here are my settings:
I have path for ftp \SAOPReplication\ftp
Just the same as for SNAPSHOT.
Should tha path be different?
"Paul Ibison" wrote:

> Sorry to ask the obvious, but are your FTP settings done correctly on the
> merge publication (inc folder paths).
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Uros,
please can you post up the results of sp_helpmergepublication and
sp_helppublication for the merge and snapshot publications.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul!
Here are the results of those store procedures.
I hope you can sort this out on notepad. I've tried and it worked.
id name
description
status retention sync_mode allow_push allow_pull allow_anonymous
centralized_conflicts priority snapshot_ready
publication_type pubid snapshot_jobid
enabled_for_internet dynamic_filters has_subscription
snapshot_in_defaultfolder alt_snapshot_folder
pre_snapshot_script
post_snapshot_script
compress_snapshot ftp_address
ftp_port ftp_subdirectory
ftp_login
conflict_retention keep_partition_changes
allow_subscription_copy allow_synctoalternate validate_subscriber_info
backward_comp_level publish_to_activedirectory max_concurrent_merge
max_concurrent_dynamic_snapshots
------
-----------
-- -- -- -- -- --
-- -- --
-- --
-- -- --
-- --
-----------
-----------
-----------
------
-----------
------
-- -- --
-----------
-
-- -- --
1 MERGE_STRANKE_SAOPsf
Merge
publication of SAOPsf database from Publisher PC.
1 14 0 1 1 1
1 100.0 1 0
817F7880-1B66-4C7E-8D8D-1AD3270328B7
0x679F4FFFFA5CAE418DC4919151EBD05A 1 0 0
0 \\PC\D$\SAOP\Replikacije
NULL
NULL
1 PC
21 \SAOPreplikacije\ftp
SQLRemote
14 0 0
0 NULL
40 0
0 0
pubid name
restricted
status task replication frequency synchronization method description
immediate_sync enabled_for_internet allow_push allow_pull
allow_anonymous independent_agent immediate_sync_ready allow_sync_tran
autogen_sync_procs snapshot_jobid retention has
subscription allow_queued_tran snapshot_in_defaultfolder alt_snapshot_folder
pre_snapshot_script
post_snapshot_script
compress_snapshot ftp_address
ftp_port ftp_subdirectory
ftp_login
allow_dts
allow_subscription_copy centralized_conflicts conflict_retention
conflict_policy queue_type backward_comp_level publish_to_AD
------
-- -- -- -- --
-----------
-- -- -- -- --
-- -- -- --
-- -- --
-- --
-----------
-----------
-----------
------
-----------
------
-- -- -- --
-- -- -- --
2 SNAPSHOT_ARTIKLI_SAOPsf
0 1
1 1 0 Snapshot
publication of SAOPsf database from Publisher PC.
1 1 1 1 1
1 1 0 0
0x30961C9177CEEF4AA8EDF9FE69CC7E01 336 1 0
0 \\PC\D$\SAOP\Replikacije
NULL
NULL
1 PC
21 \SAOPReplikacije\ftp
SqlService
0 0 NULL
14 NULL NULL 10 0
|||Can the subscriber resolve the host name PC to the FTP Server? It probably
needs to be a Fully Qualified Domain Name like PC.MyDomain.Com, or you need
a hosts file entry mapping PC to the IP address of the FTP server.
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
"uros" <uros@.discussions.microsoft.com> wrote in message
news:3D947F9B-2DA3-4C75-9860-1401E33EEB3C@.microsoft.com...
> Hello!
> I'm doing replication over non-trusted domains. I'm using FTP server to do
> that.
> I've also read Paul's articel about replication over non - trusted
> domains.
> I'm using snapshot and merge replication.
> Snapshot replication works OK, without any problems, but MERGE replication
> gives me this error:
> The schema script '' could not be propagated to the subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> ------
> The process could not connect to FTP site 'PC' using port 21.
> (Source: STREZNIK\SAOP (Agent); Error number: 0)
> ------
> Can you help me,
> Uros
|||Hilary!
I've done that. I've updated the host file. And as I said, SNAPSHOT
replication works fine via FTP, but merge replication fails with that error.
I don't know, how to continue and I have a deadline.
U.
"Hilary Cotter" wrote:

> Can the subscriber resolve the host name PC to the FTP Server? It probably
> needs to be a Fully Qualified Domain Name like PC.MyDomain.Com, or you need
> a hosts file entry mapping PC to the IP address of the FTP server.
> --
> 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
> "uros" <uros@.discussions.microsoft.com> wrote in message
> news:3D947F9B-2DA3-4C75-9860-1401E33EEB3C@.microsoft.com...
>
>
|||Uros,
sorry - even in notepad this is pretty difficult. Please can you set the
query analyser to output the results to text and use a Pipe delimiter, then
repost the results.
Cheers,
Paul Ibison
"uros" <uros@.discussions.microsoft.com> wrote in message
news:3D470926-AEBC-48BB-9875-F2FA879D2CA0@.microsoft.com...
> Paul!
> Here are the results of those store procedures.
> I hope you can sort this out on notepad. I've tried and it worked.
> id name
> description
>
> status retention sync_mode allow_push allow_pull
> allow_anonymous
> centralized_conflicts priority snapshot_ready
> publication_type pubid snapshot_jobid
> enabled_for_internet dynamic_filters has_subscription
> snapshot_in_defaultfolder alt_snapshot_folder
>
> pre_snapshot_script
>
> post_snapshot_script
>
> compress_snapshot ftp_address
> ftp_port ftp_subdirectory
>
> ftp_login
> conflict_retention keep_partition_changes
> allow_subscription_copy allow_synctoalternate validate_subscriber_info
>
> backward_comp_level publish_to_activedirectory max_concurrent_merge
> max_concurrent_dynamic_snapshots
> --
> ------
> ----------
--
> -- -- -- -- -- --
> -- -- --
> -- --
> -- -- --
> -- --
> ----------
--
> ----------
--
> ----------
--
> --
> ------
> --
> ----------
--
> ------
> -- -- --
> --
> ----------
--
> -- -- --
> --
> 1 MERGE_STRANKE_SAOPsf
> Merge
> publication of SAOPsf database from Publisher PC.
>
> 1 14 0 1 1 1
> 1 100.0 1 0
> 817F7880-1B66-4C7E-8D8D-1AD3270328B7
> 0x679F4FFFFA5CAE418DC4919151EBD05A 1 0 0
> 0 \\PC\D$\SAOP\Replikacije
>
> NULL
>
> NULL
>
> 1 PC
> 21 \SAOPreplikacije\ftp
>
> SQLRemote
> 14 0 0
> 0 NULL
>
> 40
> 0
> 0 0
> pubid name
> restricted
> status task replication frequency synchronization method
> description
>
> immediate_sync enabled_for_internet allow_push allow_pull
> allow_anonymous independent_agent immediate_sync_ready allow_sync_tran
> autogen_sync_procs snapshot_jobid retention has
> subscription allow_queued_tran snapshot_in_defaultfolder
> alt_snapshot_folder
>
> pre_snapshot_script
>
> post_snapshot_script
>
> compress_snapshot ftp_address
> ftp_port ftp_subdirectory
>
> ftp_login
> allow_dts
> allow_subscription_copy centralized_conflicts conflict_retention
> conflict_policy queue_type backward_comp_level publish_to_AD
> --
> ------
> -- -- -- -- --
> ----------
--
> -- -- -- -- --
> -- -- -- --
> -- -- --
> -- --
> ----------
--
> ----------
--
> ----------
--
> --
> ------
> --
> ----------
--
> ------
> -- -- -- --
> -- -- -- --
> 2 SNAPSHOT_ARTIKLI_SAOPsf
> 0
> 1
> 1 1 0 Snapshot
> publication of SAOPsf database from Publisher PC.
>
> 1 1 1 1 1
> 1 1 0 0
> 0x30961C9177CEEF4AA8EDF9FE69CC7E01 336 1 0
> 0 \\PC\D$\SAOP\Replikacije
>
> NULL
>
> NULL
>
> 1 PC
> 21 \SAOPReplikacije\ftp
>
> SqlService
> 0 0 NULL
> 14 NULL NULL 10 0
>

Merge Replication issue .. Please help (Replication does not work)

How is the network relationship set up? If this is a non-
trusted relationship, you'll need to register an alias in
the client network utility on the subscriber, and place
an entry in the hosts file there also.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Paul,
Thank you for your reply.
This is a non-trusted relationship.I registered a client network utility
with the alias pointing to my publisher/ distributor and added an entry in
the host file also.
But still I 'm getting this same message in the job history:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
What is wrong am I doing?
Sam
"Paul Ibison" wrote:

> How is the network relationship set up? If this is a non-
> trusted relationship, you'll need to register an alias in
> the client network utility on the subscriber, and place
> an entry in the hosts file there also.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Also I tried to push the subscription instead of pullin git from subscriber.
But in push subscription , the merge agent throws this error:
The remote server is not defined as a subscription server.
How do I set up the remote server as subscription server?
The merge agent does transfers lot of data and objects from publisher to
subscriber , it is sometime at the end of the process , it fails.
Please advice..
Sam
"Paul Ibison" wrote:

> How is the network relationship set up? If this is a non-
> trusted relationship, you'll need to register an alias in
> the client network utility on the subscriber, and place
> an entry in the hosts file there also.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Sam,
have you set up FTP for the initialization? Have a look at this article:
http://support.microsoft.com/?id=321822
Also, check that the correct port has been opened up on the firewall (port
1433 for default instance of SQL Server, by default).
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Merge replication in 'SQL Server'

Hi,
I read Paul Ibison's article about "Replication Across Non-Trusted Domains
or Using the Internet".
Me (and my company) need to take a very tough decision whether using SQL
server 2005 merge replication or building our own synchronization engine.
Our big problems are:
1. Everything has to work over the internet (over port 443 only), even port
21 for ftp is not an issue…
2. Out product is for customers overseas without the ability to go through
an integration process at the client site. It means we must use some
automatic process configuring the publisher or subscriber and users running
processes, etc.
3. The installation must work from an installation cd (both client and
server), without the need to manually configure domain users to run certain
replication agents – it must also be automatically.
Which one (or all) of the demands above is possible?
We are willing to make small changes –only after we definitely know that we
must open port 21 for example.
I understood that the implementation of offline clients (doesn't matter if
it's PDA with SQL CE/Mobile or windows XP with MSDE/Express) and Merge
replication in the SQL Server is good in theory but difficult to manage and
requires a lot of extra handling issues like opening ports and adding users
granted to run the processes for the replication process.
Are there any improvements in 2005 in these issues (I know about the option
to replicate through iis so the port problem is now solved?!).
My most important request is that I'll be glad if anybody knows and can
write about products in the open market which used this architecture.
Thanks,
Gil.
I'm in a crucial
Is it true? Are there any improvements in 2005 in these issues (I know about
the option to replicate through iis so the port problem is now solved?!).
I'll be glad if anybody knows and can write about products in the open
market which used this architecture.
Thanks,
Gil.
1) no problem, you can configure sql server to run on any port - have a
look at http://support.microsoft.com/default...b;en-us;823938 in
the section marked. However, port 443 is for https, did you want your SQL
Server traffic encrypted?
Configuring an instance of SQL Server to use a static port
2) you can script out replication jobs by right clicking on a publication
and selecting - generate sql script. You can generate the scripts necessary
to enable replication by right clicking on the replication folder and
selecting Generate SQL Scripts, and then selecting Distributor properties.
3) you can configure autorun.inf to run an executable which will run the
scripts generated above
Everything you list is possible - you suddenly start talking about SQL CE -
if your clients are running SQL CE, you will need a web server to
synchronize with. You could run over port 443 for this. I would not
characterize "Merge replication in the SQL Server is good in theory but
difficult to manage and requires a lot of extra handling issues like opening
ports and adding users granted to run the processes for the replication
process."
This is simply not true. Merge replication or any form of replication only
needs port 1433 (or whatever port you run SQL Server on) open. If you are
deploying your snapshot over the internet you will probably want port 21
open as well. Regarding the addition of users, this could be valid. You can
run pull agents on the subscribers which will connect to the publisher under
different accounts if you are doing filtering by suser_name(). But by
default you probably would not have to do this. I normally use pass through
authentication which uses the same account names.
There are lots of improvements, fixes, and features in SQL 2005. Web
synchronization is one of them. Although the documentation talks about
running over port 1433 (https) in addition to 80(http), I believe this is a
mistake.
I worked on a replication topology with over 60 merge clients. We had our
share of problems, but in general it was highly stable.
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
"Gil" <Gil@.discussions.microsoft.com> wrote in message
news:123D2E11-371E-419E-8B5F-D4710F95A008@.microsoft.com...
> Hi,
> I read Paul Ibison's article about "Replication Across Non-Trusted Domains
> or Using the Internet".
> Me (and my company) need to take a very tough decision whether using SQL
> server 2005 merge replication or building our own synchronization engine.
> Our big problems are:
> 1. Everything has to work over the internet (over port 443 only), even
port
> 21 for ftp is not an issue.
> 2. Out product is for customers overseas without the ability to go through
> an integration process at the client site. It means we must use some
> automatic process configuring the publisher or subscriber and users
running
> processes, etc.
> 3. The installation must work from an installation cd (both client and
> server), without the need to manually configure domain users to run
certain
> replication agents - it must also be automatically.
> Which one (or all) of the demands above is possible?
> We are willing to make small changes -only after we definitely know that
we
> must open port 21 for example.
> I understood that the implementation of offline clients (doesn't matter if
> it's PDA with SQL CE/Mobile or windows XP with MSDE/Express) and Merge
> replication in the SQL Server is good in theory but difficult to manage
and
> requires a lot of extra handling issues like opening ports and adding
users
> granted to run the processes for the replication process.
> Are there any improvements in 2005 in these issues (I know about the
option
> to replicate through iis so the port problem is now solved?!).
> My most important request is that I'll be glad if anybody knows and can
> write about products in the open market which used this architecture.
> Thanks,
> Gil.
>
> I'm in a crucial
> Is it true? Are there any improvements in 2005 in these issues (I know
about
> the option to replicate through iis so the port problem is now solved?!).
> I'll be glad if anybody knows and can write about products in the open
> market which used this architecture.
> Thanks,
> Gil.
>
>
|||Thank you for your answer...
But I guess I wasn't completely clear.
We plan to use merge replication with new web replication feature available
in "SQL server 2005", and I wanted to know whether there is an option to work
with SSL over http without the need for opening the ftp port?
We definitely cannot open port 1433 because the replication will go over the
internet – and Windows authentication is not possible too.
There is also a need to use SUSER_SNAME() function in order filter by the
connected user. Is there a workaround of doing it without giving special
permissions to the user? I noticed there are security problems impersonating
the users just like that, these are the most annoying parts
Thanks,
Gil.
"Hilary Cotter" wrote:

> 1) no problem, you can configure sql server to run on any port - have a
> look at http://support.microsoft.com/default...b;en-us;823938 in
> the section marked. However, port 443 is for https, did you want your SQL
> Server traffic encrypted?
> Configuring an instance of SQL Server to use a static port
> 2) you can script out replication jobs by right clicking on a publication
> and selecting - generate sql script. You can generate the scripts necessary
> to enable replication by right clicking on the replication folder and
> selecting Generate SQL Scripts, and then selecting Distributor properties.
> 3) you can configure autorun.inf to run an executable which will run the
> scripts generated above
> Everything you list is possible - you suddenly start talking about SQL CE -
> if your clients are running SQL CE, you will need a web server to
> synchronize with. You could run over port 443 for this. I would not
> characterize "Merge replication in the SQL Server is good in theory but
> difficult to manage and requires a lot of extra handling issues like opening
> ports and adding users granted to run the processes for the replication
> process."
> This is simply not true. Merge replication or any form of replication only
> needs port 1433 (or whatever port you run SQL Server on) open. If you are
> deploying your snapshot over the internet you will probably want port 21
> open as well. Regarding the addition of users, this could be valid. You can
> run pull agents on the subscribers which will connect to the publisher under
> different accounts if you are doing filtering by suser_name(). But by
> default you probably would not have to do this. I normally use pass through
> authentication which uses the same account names.
> There are lots of improvements, fixes, and features in SQL 2005. Web
> synchronization is one of them. Although the documentation talks about
> running over port 1433 (https) in addition to 80(http), I believe this is a
> mistake.
> I worked on a replication topology with over 60 merge clients. We had our
> share of problems, but in general it was highly stable.
> --
> 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
> "Gil" <Gil@.discussions.microsoft.com> wrote in message
> news:123D2E11-371E-419E-8B5F-D4710F95A008@.microsoft.com...
> port
> running
> certain
> we
> and
> users
> option
> about
>
>
|||Re the port issue - I asked this question on the Beta newsgroup - for Merge
over the internet in SQL 2005, is HTTP (80) supported or must it be HTTPS
(443) and the reply was HTTPS only. (which makes it a pain fully testing the
whole process on XP which doesn't support certificate server). At the time I
noticed that the advice in BOL for the initial Beta2 version had some typos
and mixed the 2 - HTTP and HTTPS, or was at best misleading. I haven't
checked the new BOL yet on this issue.
Cheers,
Paul Ibison
|||Hi,
Can someone give me some real-world example of a product (not an IT project
- where a DBA be in the integration process, a product for customers
overseas) which is using web merge replication (over http only) ?
Doesn't matter if the Client is windows XP or mobile.
Thanks,
Gil.
"Paul Ibison" wrote:

> Re the port issue - I asked this question on the Beta newsgroup - for Merge
> over the internet in SQL 2005, is HTTP (80) supported or must it be HTTPS
> (443) and the reply was HTTPS only. (which makes it a pain fully testing the
> whole process on XP which doesn't support certificate server). At the time I
> noticed that the advice in BOL for the initial Beta2 version had some typos
> and mixed the 2 - HTTP and HTTPS, or was at best misleading. I haven't
> checked the new BOL yet on this issue.
> Cheers,
> Paul Ibison
>
>
|||Gil,
I'd also be interested to hear of any such products but I think we'll be
lucky - SQL Server's only in Beta2 at this stage
HTH
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)