Re: Help on synch to SQL server



M -

You are mostly correct. The only point in your list that I want to clarify
is that when you "dock your device", synchronization through IIS does
not automatically occur. You initiate merge replication or remote data
access
from SQL CE to SQL Server from your smart-device application's code.
This can occur whenever the device has a network path to IIS, whether
that be through Activesync passthrough, 802.11, GPRS, etc.

Unlike merge replication between SQL Servers where you can use RMO
or an ActiveX control to achieve replication without IIS, SQL CE uses
IIS as the gateway through which replication occurs to provide the best
combination of accessibility in the face of a variety of connectivity
scenarios. It can also be secured with SSL although this is not required
(as is web synch with RMO).

Other than that, it seems you have a good understanding of how to get
started with replication and SQL Server CE. Let us know if you run
into any difficulty.
--
Darren Shaffer
..NET Compact Framework MVP
Principal Architect
Connected Innovation
www.connectedinnovation.com


"M Reilly" <m_reilly@xxxxxxxxxxx> wrote in message
news:dcj238$ehh$1$8300dec7@xxxxxxxxxxxxxxxxxxx
>I have written a program for Pocket PC 2003 using visual studio and a
>pocket
> access database. Ideally I would like to use Sql CE to synch with a SQL
> Server 2000 database. My development machine is running Windows 2000
> Professional and has PWS, SQL server 2000 development edition and Visual
> studio.net
>
> By reading information on the web it looks like I need to
>
> - Load the SQL Server CE 2.0 Server Tools on a machine that is running
> IIS,
> which loads the SQL Server CE Connectivity Management utility and the SQL
> Server CE Virtual Directory on the IIS server.
>
> - Set up SQL Server as a Publisher/Distributor for replication and a
> snapshot folder defined with the appropriate permissions, and set up a
> database for CE.
>
> - Write an application that uses SQL CE in visual studio. When the code it
> depolyed to the Pocket PC device it should install the application on the
> device as well as SQL CE
>
> - When I dock the portable device is should synch though IIS with the SQL
> server.
>
> Is the above correct, and is IIS needed rather than PWS ? Also, why is IIS
> required and is there not a way to synch directly with SQL server ?
>
> Any help with the above or advice greatfully received.
>
> Thanks in advance,
>
> Mark
>
>


.



Relevant Pages

  • Re: Internet Sync with TSI
    ... intranet to synch the hubs. ... replication as I don't have a good feeling about Jet ... TSI may indeed be more feature rich; but incorporating it into code is ... looking at SQL Server replication). ...
    (microsoft.public.access.replication)
  • Re: manual installation of sqlce server agent on iis 6.0
    ... Configuring IIS Manually for Replication and RDA ... SQL Server CE v2.0 Agent must be specified as part of the ...
    (microsoft.public.sqlserver.ce)
  • Re: New to Merge/Replication
    ... ADO.NET 3.0 includes "Synchronization Services" that does not require IIS. ... Hitchhiker's Guide to Visual Studio and SQL Server ... It was my deepest hope that Merge/Replication between SQL Compact Edition and SQL Server 2005 Enterprise Edition would have it's own sync services NOT dependent on IIS. ... You can use merge replication with SQL Server on your main desktop serving as the publisher with SQL Compact on PPC, TabletPC, or other desktops as subscribers, so that would probably be the easiest solution for you. ...
    (microsoft.public.sqlserver.ce)
  • Re: CE & merge replication
    ... Beware that after changing the logging level on the registry, ... >> running IIS. ... >>> I am using merge replication between SQL Server 2K and CE. ...
    (microsoft.public.sqlserver.ce)
  • Re: SMS_MP_CONTROL_MANAGER error 4960
    ... When I try to restart the IIS it says nothing.... ... Manually restart the SMS Agent Host service on the MP. ... MP encountered an error when connecting to SQL Server. ... The Default Web Site is disabled in IIS. ...
    (microsoft.public.sms.setup)