RE: Roll your own xtranet msde replication - Whats really required

Thanks for your reply Donald,
yep the dividing up is valid. probably more than is curently being done.
I thread.sleep(n) during a "transaction" which as steps include:
are you there? heres what I have to say and how big, did you get it? and how
much? got anything for me? howmuch?, getting it, this is what I got, was it
right?
good, Ill que it to the update db process.
thread end.

I was more asking in this forum, for the viewpoint of whether some
fundamental intrinsic msde, sql server functionality had been overlooked
that had I looked a little further a lot of time could have been saved. for
example, why wasn't sql over http (checking injection of course) using the
sql isapi functionality mounted on iis (tsql books on line) good enough.
Could it really be that simple?
--
Rich Wood
MCSD


"Donald Welker" wrote:

> What's your definition of "better"? For example you could wire up a message
> queue to do the same thing via SMTP and let mail servers handle the delivery
> for you, similarly you could use ftp (heck, you could even use UUCP!) not
> that I'd want to code any of it. You have to trade bandwidth for timeliness
> of updates (and there's that pesky security issue to deal with.)
>
> Your concern seems to be maximizing the speed of the update replication
> where the remote clients cannot advertise their own services -- therefore
> they have to advertise their data via postbacks to the master server. Would
> it help to split this into steps such that a client posts that it has data,
> then the server updates a flag when it is ready for the data to be posted,
> then the client posts its data? That would enable the server to serialize
> the postings rather then having all remote clients try to postback the
> instant they have an update. Having the client query the flag every n
> seconds might be much lower bandwidth than all of them contending to post at
> once.
>
> "fleetfingers" wrote:
>
> > Greetings from Austin.
> > I have a number of remote msde's which need to replicate rows to a master
> > sql server instance located behind a static ip accessible through a
> > webmethod.
> > the remote msde's are non static ips and can only make requests. A Windows
> > service runs on each of the remote machines where changed rows are gathered
> > from the database within msde, the selects are bagged into various xml
> > stuctures and the call is made to the webmethod. Web method has 2 params
> > calltype (an int) and payload (a string). These type requests are made on a
> > clock by the windows service. Similarly requests are made using a different
> > call type where updates from the sql server trickle down in a structure and
> > are assimilated by the remote windows service, into the msde.database. My
> > question for the groups is Is there a better way to accomplish (essentially)
> > replication between a sql server and her flock of msdes? Has anyone done
> > similar extranet replication in a different way?
> > Best from Austin.
> >
> > Rich Wood
> > MCSD
.

Relevant Pages

  • Re: TS vs VPN
    ... Using TS, w/o VPN ... The remote client connects to your local TS via Remote Desktop. ... "Foo" accesses the SQL server, which is nearby in a protected part of the network. ...
    (microsoft.public.windows.terminal_services)
  • Re: Which hardware upgrades are more important
    ... remote connection to SQL Server can be secured to similar levels. ... no way to serve up Jet data to an Access front end to remote ... One client, before being convinced to use TS, connected their remote office WAN via a broadband microwave link. ... The users still complained that the app was almost unusable (MDB BE at the time, currently SQL Server). ...
    (comp.databases.ms-access)
  • Re: Quick Question on SQL Server 2005 Express
    ... I have been away all week, but I can report that I did manage to connect to the "remote" version of SQL Server. ... I have now set up an Express version on our LOCAL server, and have linked a second Express version to this server via the network, as above for my client. ... We had discussed having our own licenced copy SQL Server 20052008, but with the cost etc, it was suggested that we use the licenced central server and a copy of Express to just hook up and do a bit of manipulation of our database. ...
    (microsoft.public.sqlserver.setup)
  • Re: Quick Question on SQL Server 2005 Express
    ... you can't attach a database in a remote machine in your network as Andrew has already mantioned. ... One database can be used only by one SQL Server instance and as far as I understand the database in question is already attached to a SQL Server instance. ... Why not installing only SQL Server Management Studio and connect to your remote instance and perform actions this way? ... The Client can live anywhere as long as it has TCP access to the server. ...
    (microsoft.public.sqlserver.setup)
  • Re: Multi-threaded Worker Objects
    ... If you can elaborate how your remote object return values to ... in turns spawn worker threads (say, 1 new thread per new client). ... My application is basically a windows service, ... Due to the way I coded the work class - and furthermore the object class ...
    (microsoft.public.dotnet.framework.remoting)