Timeline for Aggregating Multiple COTS Databases into a Data Warehouse or similar for Reporting
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 7, 2019 at 7:49 | answer | added | Trubs | timeline score: 2 | |
| Aug 6, 2019 at 17:30 | comment | added | CPickler | Preferably both. We absolutely want to move the load off the production boxes, but we don't want to stand up 14 new servers for the data warehouse solution. So we'd like to move them all to one large server, which would have the added benefit of all the information being in one place. | |
| Aug 6, 2019 at 17:28 | comment | added | CPickler | Trubs - Old data is never modified but new data is added. So the tracking changes would be for DB 1 & 2. | |
| Aug 6, 2019 at 8:34 | comment | added | Trubs | What is the actual goal here? is it to remove the load from the production boxes (or maybe just the production databases), or is it to centralise your reporting so all the information is in one place (so you can do geographic comparisons?) | |
| Aug 6, 2019 at 8:30 | comment | added | Trubs | Hi CPickler - You mention that old data is never modified (database 3), yet in the 2nd para, you mention that you'd like to track changes? If it doesn't change, what are you tracking? | |
| Aug 6, 2019 at 3:15 | review | First posts | |||
| Aug 6, 2019 at 6:43 | |||||
| Aug 6, 2019 at 3:11 | history | asked | CPickler | CC BY-SA 4.0 |