General discussion



By flyingknees ·
I'm not sure if this classifies as redundancy but I currently have two SQL 2000 databases running on Windows 2000 Servers. Each server is at a geographically separate location and they (or the sites) are linked by a dedicated T-1.

Clients want to access the database through a web portal I have. However in order for them to get to the database at the other location, it needs to be routed through the T-1. Is there a better way of caching that remote database locally? I think clustering may help but the remote database also contains hundreds and hundreds of scanned images that also needs to be cached locally. Is there anyway to do this in real-time or near real-time so that the Internet client will be accessing a local replica of that remote database and all of its files?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by ross.bale In reply to Redundancy?

Assuming the two database servers are running the same database, the easiest way would be to build a small SAN split across the two sites, with each Database server running just the application, and the data pointing to the SAN, there would only be 1 live database which would be split for redundancy and would not require updates. If one server/site went down the other would simply take over.

Collapse -

by flyingknees In reply to

Poster rated this answer.

Collapse -

by flyingknees In reply to Redundancy?

This question was closed by the author

Related Discussions

Related Forums