New answers tagged

0

I think you'll have better luck creating separate VMs for each release/subproject. That way you have a completely contained and isolated environment (DB, source, test data, etc). If you keep the VM images on shared storage somewhere, then it makes it easy for someone else to grab a copy of the image if you'd like to have them take a look at it. If you're ...


1

Triggers fire synchronously with the transaction which wrote the data initially. That Tx will incur further latency because of the trigger. This may be acceptable to you, or not. If the trigger code fails the original Tx will fail too. Change Data Capture may be a reasonable approach. It can be asynchronous at runtime. The application will be ignorant of ...


1

The cost of ETL should be cheaper because there's some level of batching involved, rather than doing work for every INSERT/UPDATE. But as the time requirement becomes smaller, trigger becomes more suitable answer. On the other hand, if it can be implemented using trigger (e.g. copy to another table), maybe you don't really need to use ETL. You need ETL to ...



Top 50 recent answers are included