I found a relative post very interesting
http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/b73b6568-dc34-4c89-9979-7f9a0c8e1dc5
but need some more information on this topic.
"regularly scans the T-Log" What about the latency? less than 3 seconds?
I need to assess these solutions in terms of license fees and compliance to our needs.
1a: SSIS: Integration Services as ETL for CDC purpose
1b: Replication feature: mirroring (Primary, Mirror ans Witness)
2: Talend Integration Suite as ETL for Change Data Capture
We can not afford clustering.
Our specific configuration applies to a very small network of WinXP workstation machines in a WORKGROUP (from 2 to 5 machines)
Dealing with a very small database (one hundred of tables): we need to synchronize 30 tables; most of them contains less than 100 rows! some historical tables contain a maximum of 200 000 rows. That's why we work with the Express version of SQLServer!
However we need to have a backUp database in case the primary machines crashes, with very few latency as far as synchronization is concerned. The mirror machine would take the role of the previous primary one (same IP, same ftp server synchronized, same software).
Role changes should operate in less than 5 minutes after the mirror machines restarts (changing IP, launching database and so on).
Any comments about the pros and cons of these solutions?
The primary machines serves database access on the workgroup. The mirror machine could stop and restart and need to retrieve missing information. How does it works with SIIS/CDC and with mirroring feature (SQL Agent) when the "mirror" machines restarts? redo logs to get back missing data?
Kind regards
JNB