This is a discussion on server sizing for 3 terabytes within the SQL Server Data Warehousing forums, part of the Microsoft SQL Server category; --> I expect a 3 terabyte warehouse would need no less than 8 processors 32 GIG ram SAN storage for ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I expect a 3 terabyte warehouse would need no less than 8 processors 32 GIG ram SAN storage for data, logs, backups Note: Analysis Services on the same box. Hits coming from ProClarity, Excel and Crystal. What do you think? d. |
| |||
| I think you haven't given nearly enough detail to have an informed opinion. It depends on many things, design, SLA, reporting requirements, toolset, detailed hardware configuration, etc. For example, I've seen a 200GB data warehouse far more resources that what you have defined. How much data is held is simply a matter of disk space the tough part is response time. Ray "d" <d@d.com> wrote in message news:d9BMd.2110$uc.2007@trnddc05... >I expect a 3 terabyte warehouse would need no less than > 8 processors > 32 GIG ram > SAN storage for data, logs, backups > > Note: Analysis Services on the same box. Hits coming from ProClarity, > Excel > and Crystal. > > What do you think? > > d. > > > |
| |||
| Ray, assume you have a good star schema, a clean set of fact tables and proper indexing. now would you care to guess? BTW: MS has a case study where they had a 2.7 T. OLAP running side by side a 1.5 T. OLTP db. guess what? 12 CPUs and a measley 16 Gig memory. d. "Ray" <someone@nowhere.com> wrote in message news > I think you haven't given nearly enough detail to have an informed opinion. > It depends on many things, design, SLA, reporting requirements, toolset, > detailed hardware configuration, etc. For example, I've seen a 200GB data > warehouse far more resources that what you have defined. How much data is > held is simply a matter of disk space the tough part is response time. > > Ray > > "d" <d@d.com> wrote in message news:d9BMd.2110$uc.2007@trnddc05... > >I expect a 3 terabyte warehouse would need no less than > > 8 processors > > 32 GIG ram > > SAN storage for data, logs, backups > > > > Note: Analysis Services on the same box. Hits coming from ProClarity, > > Excel > > and Crystal. > > > > What do you think? > > > > d. > > > > > > > > |
| ||||
| d, No. Still only a fraction of the information needed to have an informed opinion. Keep in mind that company's are corted by MS to produce marketing material called white papers. While not all whitepapers are marketing material the ones that say "look what we accomplished" are. They can provide some good insight but it's what they don't mention that is more interesting. Ray "d" <d@d.com> wrote in message news:z2fOd.16828$wc.12224@trnddc07... > Ray, > > assume you have a good star schema, a clean set of fact tables and proper > indexing. now would you care to guess? > > BTW: MS has a case study where they had a 2.7 T. OLAP running side by side > a > 1.5 T. OLTP db. > guess what? 12 CPUs and a measley 16 Gig memory. > > d. > > "Ray" <someone@nowhere.com> wrote in message > news >> I think you haven't given nearly enough detail to have an informed > opinion. >> It depends on many things, design, SLA, reporting requirements, toolset, >> detailed hardware configuration, etc. For example, I've seen a 200GB >> data >> warehouse far more resources that what you have defined. How much data >> is >> held is simply a matter of disk space the tough part is response time. >> >> Ray >> >> "d" <d@d.com> wrote in message news:d9BMd.2110$uc.2007@trnddc05... >> >I expect a 3 terabyte warehouse would need no less than >> > 8 processors >> > 32 GIG ram >> > SAN storage for data, logs, backups >> > >> > Note: Analysis Services on the same box. Hits coming from ProClarity, >> > Excel >> > and Crystal. >> > >> > What do you think? >> > >> > d. >> > >> > >> > >> >> > > |