Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / November 2003

Tip: Looking for answers? Try searching our database.

Web Services vs SQl Server Replication (repost)

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Simon Kewin - 20 Nov 2003 09:41 GMT
Reposted as I didn't use my Microsoft-provided posting
address ...

I'm interested on any opinions people have. If I have
a .net rich-client app that operates in a disconnected
fashion and that needs to synchronize as and when it can
with a central SQL Server, what sort of approach would you
take? What are the pros and cons of the various
approaches?

1. Install SQL onto client machines and use SQL
Replication across the internet via HTTP. A potential
security problem?

2. Use SQL Replication across a VPN?

3. Develop a Web Service based system that passes ADO.Net
DataSets around and uses their merge functionality?

4. Some other approach I haven't thought of?

Thanks in advance.
MSFT - 21 Nov 2003 02:44 GMT
Hi Simon,

If the data which needs to synchronize are not very much, you can consider
pass a dataset via WEB service and HTTPS. If the data are huge, I suggest
you may consider SQL replication with VPN, it is more stable on this issue.

Luke
Microsoft Online Support

Signature

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Simon Kewin - 21 Nov 2003 12:43 GMT
Hi Luke,

Thanks for the reply. As to HTTPS - I was thinking of
encryption at the message level using WSE (or WSE 2 as and
when it appears. Do we know whan that might be by the
way?). Can you flesh out your reasoning a little? Is it
because the WS route is "better" (easier? more robust?
more generic?) but that large amounts of data would be
more efficiently processed by direct SQL calls?

Simon.

>-----Original Message-----
>Hi Simon,
[quoted text clipped - 11 lines]
>
>.
MSFT - 24 Nov 2003 10:26 GMT
Hi Simon,

For web service solution, it is more flexible and easier to manage. You
don't need to build replication or even install a SQL server on your
client, you can get the data from multile clients. However, if the data is
huge, it may not be suitable for tranfer via http, the reponse may take a
long time and the data may get lost. SQL replication is more suitable at
this time.

Hope this help,

Luke
Microsoft Online Support

Signature

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)


Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.