Hi Al,

How big is the database in total?

Are the documents zipped in the database? In our app, we zip documents and unzip at the client end. That should reduce the neccesary bandwidth.

How large is the distance between the different sites? If limited to less than a 1000 km, a single database server might be sufficient.
Your app otoh, should be optimized to have limited calls to the SQL server through.


In our app, one of the clients is 3000km away from the database with reasonable performance.

I can see this work, but it depends on the chattiness of your application, the stability of the internet connection, and the number of users involved at each site


Wallter,



>>At that low bandwidth at the branches, having a connection via Citrix would be the way to go and only have one central server. Trying to replicate over that low bandwidth will be trouble for that data volume potential.
>
>Yes, it turns out the solution provider isn't willing to support replication over low bandwidth, so it's going to have to be some sort of remote access setup.
>
>Embedding documents in the database doesn't happen every day. They might go for a while not doing any, and then have to put in one or two dozen.
>
>Do you have any idea of the efficiency of replication in this sort of scenario? If a 1MB document is embedded, how large of a transaction log entry does that create - I wonder if there's significant bloat.