Timeline for best ETL design to transfer transaction tables records into the data-warehouse
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 10, 2015 at 15:33 | comment | added | Jon of All Trades |
+1. I've used these techniques successfully on a small-to-medium-sized (10s of millions of records) warehouse. Note that you can also cap your loads; e.g., select the first X records ordered by the ROWVERSION field, so you know your ETL will never attempt to move more than it can handle. If the system falls behind for any reason, it's better to catch up gradually than to try to import more than it can handle and fail when your log file fills up.
|
|
| Sep 1, 2013 at 18:19 | history | edited | r.m | CC BY-SA 3.0 |
added 2 characters in body
|
| Sep 1, 2013 at 17:50 | history | edited | r.m | CC BY-SA 3.0 |
deleted 16 characters in body
|
| Sep 1, 2013 at 17:45 | history | edited | r.m | CC BY-SA 3.0 |
deleted 16 characters in body
|
| Sep 1, 2013 at 17:38 | history | answered | r.m | CC BY-SA 3.0 |