Replication solutions?

Hello everybody

I work at a company in Iceland and we have developed a 3-tier solution
written in ASP - Visual Basic - MSSQL2000, 4 companies are using the
solution almost constantly and accessing it through a browser. The
connection has never gone down (yet) so that it has affected our
clients but we are thinking of how be able to run the solution locally
at every place and then create a replication to a main server that is
hosted at our place.

My question is: Does it affect speed for the clients that are using
the solution or is there a better way of doing this?

The solution is a ticket sale system and our clients use it every day
and people that sit at home should be able to order ticket online.
Because of that we can't update the database every 5 minutes or 15
minutes because we don't want a double booking in the same seat.

Any help appreciated!

- Sindri"Sindri Mar" <sindri@.veldi.is> wrote in message
news:8ee9a793.0401090855.774e35cd@.posting.google.c om...
> Hello everybody
> I work at a company in Iceland and we have developed a 3-tier solution
> written in ASP - Visual Basic - MSSQL2000, 4 companies are using the
> solution almost constantly and accessing it through a browser. The
> connection has never gone down (yet) so that it has affected our
> clients but we are thinking of how be able to run the solution locally
> at every place and then create a replication to a main server that is
> hosted at our place.
> My question is: Does it affect speed for the clients that are using
> the solution or is there a better way of doing this?
> The solution is a ticket sale system and our clients use it every day
> and people that sit at home should be able to order ticket online.
> Because of that we can't update the database every 5 minutes or 15
> minutes because we don't want a double booking in the same seat.
> Any help appreciated!
> - Sindri

It's not clear from your description what the reason for considering
multiple local copies is. If the application is web-based, then it shouldn't
really matter where the clients are, assuming they have a good connection to
your web site. Right now you have one database to manage, but creating local
copies would create more administrative work, and replication can become
quite complex. By having one single central database, you should also find
it a lot easier to avoid duplicate bookings, because everyone always sees
the current 'real-time' data.

Having said that, if you have good reasons to consider local copies (such as
copying only a subset of data to the central site, while leaving any
confidential data locally perhaps), then replication can certainly do what
you want. It's a big topic, though, so you may want to post on
microsoft.public.sqlserver.replication to see if you can get some more
detailed advice.

Simon

Replication keeps failing after one failure

Hi,
We are running Merge Replication on Sql Server 2K with multiples MSDE 2K subsciber.The Replication is getting done through a Visual Basic Application and it works fine as long as it does not fail.Once the replication fails on the Clients machine then we always need to blow the Local Database on the Client's machine and then start the Merge Replication process again.I wonder Why?Any help is really appriciated.. :(It's necessary adjust the retry count for the merge agent, in the event it fails (e.g. remote computer is turned off, network failure etc.). Expand Replication monitor, expand agents, click on merge agents. A list of merge agents, corresponding to each location is listed on the right. To change retry count for a merge agent, highlight the merge agent, right click and select agent properties. Click on tab "Steps", Highlight ID 2 (step 2 - run agent), click on edit. Step name should say "Run agent". Click on Advanced tab, and adjust the retry count and retry interval.
:D|||Thanks for your reply and I will increase the Number of Retry but my question is still unanswered and that's Why the Replication keeps failing after one failure?Is this turning on some flag somewhere in the Sql Server after a failure?|||Ok, I'm confused.

Replication is done via a Visual Basic program?

Replication is a configuration of Sql Server. Has nothing to do with Visual Basic.

What kind of Merge replication is setup? Merge continuosly, or scheduled merge?

If Merge continuously, then the retry count and schedule HAS to be changed. The defaults will cause the agent to fail if the connection is down for just 10 minutes. (10 retries, at 1 minute intervals).

Also, when you say replication fails, there are error messages that can be viewed via replication monitor. The agent may try 10 times, and on failure display 1 message. That doesn't mean there were no retries.|||It's a Merge Replication which runs on Demand through Visual Basic Application.The process works fine 9/10 times but if its fails then it keeps failing and the error log says "The Process was Successfully Stopped".I also don't think that it involves any network issue as the subscriber is connected to the network all the time.
Also once the Synchronization fails then we need to set the Initial database at the subscriber(which involves defining the subscriber,creating the local DB,Copying Roles and creating a dynamic Merge Replication job) and then do the Regular Synchronization,which works fine thereafter.

I don't know Y?:confused: