Relational Data Warehouse or Reporting work loads are characterized by low volumes of very large transactions. These applications are often identified as having predominately read workloads (e.g. Decision Support, Analysis, and Reporting) with periodic feeds or batch loads. It is important to keep these characteristics in mind as we examine the significance of database design, resource utilization and system performance. The top performance bottlenecks or gotchas to avoid for Data Warehouse or Reporting applications are outlined below.
Database Design issue if….
Memory bottleneck if….
IO bottleneck if…
Blocking bottleneck if….
Network bottleneck if….
Wait statistics gotchas...
Watch out for fragmentation.
Consider Table Partitioning for fast loads
In contrast to OLTP, a data warehouse or Reporting application is characterized by a small number of large SELECT transactions, each very different. The implications are significant for database design, resource usage, and system performance. These distinctions result in very different objectives and resource utilization profiles.
I've talked about the SQLCAT team before and the great content they produce , you may have had a chance
I've talked about the SQLCAT team before and the great content they produce , you may have had a
Pingback from MSDN Blog Postings » SQL Server Customer Advisory Team
Pingback from DBA 101: Using Perfmon for SQL Performance Tuning : BrentOzar.com
Pingback from sqlcat.com/.../top-10-sql-server-2005-performance-issues-for-data-warehouse-and-reporting-applications.aspx
Pingback from SQL Performance tips | 2secondmemory
Pingback from Quick Analysis of SQL Performance Troubleshooting | Rich Kreider
I' ve got more thing with this object thanks for your blogs