Immediate Update of Data to Two Seperate Databases (one internal, one external)
I have the need to have a real time replica of a few of our tables that are stored in an off site location for disaster recovery.
What we would like would be whenever there is a change on table Orders on our internal sql 2000 database, that the same change is then made to the table Orders on a database stored externally, probably by GoDaddy or some similar host.
All changes currently are completed via web pages using classic asp, so if needed, I can just add update / insert statements to the code of the pages, but I'd prefer to do a trigger on the sql side.
So, is it possible to do a sql trigger from a local database to an external database hosted by, say, GoDaddy? Do we need to do any upgrades of our existing sql-2000 server?
Are there any other solutions you can think of to achieve what we are looking for?
In a nutshell, we want to have a real time replica of some tables we choose, we could do the entire database is that is easier also, but it isn't needed.
What we would like would be whenever there is a change on table Orders on our internal sql 2000 database, that the same change is then made to the table Orders on a database stored externally, probably by GoDaddy or some similar host.
All changes currently are completed via web pages using classic asp, so if needed, I can just add update / insert statements to the code of the pages, but I'd prefer to do a trigger on the sql side.
So, is it possible to do a sql trigger from a local database to an external database hosted by, say, GoDaddy? Do we need to do any upgrades of our existing sql-2000 server?
Are there any other solutions you can think of to achieve what we are looking for?
In a nutshell, we want to have a real time replica of some tables we choose, we could do the entire database is that is easier also, but it isn't needed.
A directly linked trigger could cause severe problems.
The best option might be a column with a type of "rowversion". SQL will increment that value every time a row is inserted or changed. Thus, you can determine which row(s) have changed since the last time you pulled data.
Or you could use a trigger(s) to copy modified data to another "staging" table. Then periodically push the data in the staging table to the external db.
Either of those approaches allows internal updates to continue even if, for some reason, the external db is temporarily unavailable.
The best option might be a column with a type of "rowversion". SQL will increment that value every time a row is inserted or changed. Thus, you can determine which row(s) have changed since the last time you pulled data.
Or you could use a trigger(s) to copy modified data to another "staging" table. Then periodically push the data in the staging table to the external db.
Either of those approaches allows internal updates to continue even if, for some reason, the external db is temporarily unavailable.
ASKER
The sync needs to be instant (relatively instant), so I won't be able to do batch pushes to the external database. I do plan on doing daily syncs, however, to ensure everything is correct.
If the external database isn't available, and I try to do an update on the internal database table, are you saying the internal update will fail due to the trigger failing to the external database? If so, that is not good. We are fine, however, with skipping the trigger if the external database is unavailable as it will get updated in a morning batch.
In regards to latency, will it affect the speed of the update on the sql internal server? I'm hoping the user will go to a web page, make a change, and it saves the same speed, just in the background the sql server then sends an update to the external database, not affecting the user's speed on the web browsing.
If the external database isn't available, and I try to do an update on the internal database table, are you saying the internal update will fail due to the trigger failing to the external database? If so, that is not good. We are fine, however, with skipping the trigger if the external database is unavailable as it will get updated in a morning batch.
In regards to latency, will it affect the speed of the update on the sql internal server? I'm hoping the user will go to a web page, make a change, and it saves the same speed, just in the background the sql server then sends an update to the external database, not affecting the user's speed on the web browsing.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
What would be needed for the replication in terms of bandwidth? We are very limited at this time, but are upgrading soon.
Depends on the volume of data.
But SQL replication would be less overhead than any method you would write yourself, since it can use internal data formats.
But SQL replication would be less overhead than any method you would write yourself, since it can use internal data formats.
--enable identity insert
insert into
linkservername.database.sc
select * from inserted
--disable identity insert