Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / General / Data Warehousing / December 2004

Tip: Looking for answers? Try searching our database.

Physical DB Structure for large ODS

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Chris - 08 Dec 2004 13:07 GMT
OK, here's the situation:

The "data warehouse" that our ERP provider sold us has evolved into more of
an operational data store.  We are in the process of developing a more
traditional star-schema data warehouse.  The ODS is getting quite large,
currently at 150 GB.  The server has 4 SAN drives (2 for data segments, 1 for
indexes and the last for log files and extract files used to load the
database).  My two data segments are currently at 65 GB each and the index
segment is 36 GB.  Based on requirements for a new project I have at least 18
GB of additional data that I'll have to load.

My question is, are there any file size/performance considerations as these
files continue to grow?  The largest of the most frequently hit tables is
15.5 million rows in 30 GB (I know, pretty big rows, but that's what we got
from the ERP provider).  

Performance of the database overall is acceptable as we've added serveral
covering indexes for our most common report requests.

Suggestions and comments are greatly appreciated.
Rangarajan Suresh - 22 Dec 2004 16:47 GMT
Is the ODS a strict ODS, implying that you have current operational
information only and it does not have historical information? One
consideration if there is historical information is to explore archiving.
When you are designing your datawarehouse, history can be built into the
datawarehouse (as is generally done) and keep your ODS trim. Can you share
more details!

Rangarajan Suresh
www.picarossolutions.com
********************

> OK, here's the situation:
>
[quoted text clipped - 16 lines]
>
> Suggestions and comments are greatly appreciated.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.