February 2, 2010 at 7:07 am
Hi there,
for our DWH wie got 2 SQL Servers (Enterprise Edt.) and our former admin/architect constructed following:
1. Server: DWH, Reporting, Cubes
this server is hosting the dwh and is used as reporting-frontend and cube-host (excel as frontend)
2. Server: ETL. This Server is doing all the ETLs. Some Procedural-Tables just used in the ETLs are hosted there, everything else is on the dwh.
I would like to know if this is a standard architecture or if there is something preferable out there. (maybe clustering) or something like that.
Cheers,
Mitch
February 3, 2010 at 2:07 pm
Clustering is used for availability reasons, not for performance so it wouldn't be an influence in your configuration unless you wanted more uptime. It might be beneficial to separate the reporting from the database, depending on how busy the reporting is.
Out of interest, how does the spec of the ETL server compare to the DB server?
February 3, 2010 at 4:11 pm
The systems are quite similar
both are Dell PowerEdge R900 with 4x xeon-6-Core and 128GB RAM
the DWH has a total DB-Space 3,5 TB RAID10
and additionally backup-place 9TB Raid6
the ETL has 700GB DB-Space RAID 10
and 5 TB as archive for incoming file (access-logs, csv-exports from other servers, etc.)
I already know that we have to reorganise the physical storage. Separate Datastorage, Indexes, tempdb end so on. So in this stage I would like to know, if we properly should reorganise the whole structure.
For example, you could say, we may put the databases of the dwh on the etl machine and then use former the "DWH" system only for the frontends (Reporting Services and Cubes).
or... what ever would be best 🙂
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply