Does the new SQL linkage capability in Filemaker 9 make it easier to periodically publish information to a SQL database?

In our case, we have a Filemaker database of content. At present, CSV files are exported once a day from various tables and then batch imported into the SQL database that drives our website. It's inefficient and there are hundreds of thousands of records across dozens of tables, but it works reliably.

Is there a good way to improve on this using the new capabilities? Note that we don't need to see what's in the SQL database, and don't need live updating of the SQL database, only periodic synching with the Filemaker one.

Looking further ahead, is it madness to think of building a new content management system in Filemaker while retaining the web publishing from SQL?

[Note, I previously published this in the ODBC subforum by mistake, where it was ignored. Apologies if you are affected by this cross-posting]

OK. Slightly oddly I am now replying to my original post. The way to do this seems to be to use one of the two commercial utilities that synchronise Filemaker databases with SQL databases. These are SyncDeK and fmSQL Synch v2.0b.

Pricing is obscure. SyncDek asks you to contact them for a quote. fmSQL Sync say $699 per user, which seems bizarre unless they effectively mean per server.

I'll report back once I have compared them.