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 |
|
lotek
Starting Member
42 Posts |
 Posted - 2011-04-03 : 14:52:54
|
| We have a nightly ETL process that creates a number of customer databases on our SQL server. EG:ClientAClientBClientCI need to maintain this structure for a number of reasons but would also like a database that contains the information for all clients so we can report on multiple clients. It seems like the options are either to create new database and create a bunch of select statements to union the tables from each database together or to load up the data in a completely separate database (2 copies of the data). Which of these two options seem better or is there another alternative i am not seeing?Thanks! |
|
|
jeffw8713
Aged Yak Warrior
819 Posts |
Posted - 2011-04-03 : 18:57:50
|
| Could you just create a single database for all client data, and then create separate databases for each client with views that filter the data for each client?You would have to make sure each table has a client ID that you can filter on, but that shouldn't be a problem. |
 |
|
|
|
|
|
OLAP / ETL Database Question