Re: [xml-dbms] Replication
- tharter@... wrote:
>Agreed. XML is just a data transport here -- you could just as easily
> When you replicate, basically you want your master
> database/middleware to send a message to the replica every time
> DML commands are sent to the database. Certainly you need to
> represent any data to be inserted/updated and XML might be handy
> in that regard, but the real problem is recognizing every possible
> circumstance under which data might have changed in the master
> database. With an SQL database that is not always particularly
> straightforward as it involves DML, Stored procedures, triggers, etc.
use ODBC, JDBC, OLE DB, or a proprietary transport.
> That being said, I have seen and worked with some ad-hocYes. Hopefully, this doesn't happen too often...
> solutions. Dump your database or a subset of your database to
> XML, haul it over to the remote system, and import it. If its a
> reasonably small database and bandwidth isn't a problem, just
> dump the entire database and then import it. I think XMLtoDBMS
> would work pretty good for that as is, but you will still need to
> tweak your map files when the schema changes, right?