Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
awilcox1014
Starting Member
3 Posts |
 Posted - 2012-06-19 : 14:50:34
|
| Our VP of Systems has nixed using CDC to capture information from a database - due to some of the more obvious and documented reasons of high overhead. 2008R2. The Source database has some issues in that it is very old and it has no update date and time stamp on the records - which rules out some of the more traditional options we might use. The system also already has a gross amount of DB Triggers - so that has been ruled out as an option as well. Creating an Event based table update is an option, but time beats us up on that choice. I have suggested perhaps replicatig the database and then turning on CDC on the replicated copy. Not even sure that would work. Can anyone else think of any creative solutions? Alot of tables involved - and a significant amount of data. The Source is a transactional database used for collections and claims management. We have a requirement for intraday updates - as well as nightly updates.Is this enough information to make proposals (I am new to this forum)?Thanks for any thoughts.AW |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2012-06-19 : 15:35:42
|
| What are you trying to accomplish? Auditing data changes? Synchronizing data between sites/servers? Do you need to actually capture the data or just the fact that it was changed, and who did it? |
 |
|
|
|
|
|
Options to using CDC