SQL Server 2008, page compression and indexing

Jeff Smith at 17h18
17
Dec
2010
SQL Server 2008, page compression and indexing

Thought I'd share...

We are using SQL Server 2008. A staging table loaded with data from the source system had Page Compression turned on. We saw a 50% reduction in space with no significant reduction in performance. Added a clustered index and realized an additional 24% reduction in space. The index put like records together, enabling the page compression to be more efficient. And the index improved the performance.

Read more
Reply
About
This topic belongs to the forum

  • Data Warehousing and Business Intelligence based on dimensional modeling and the Kimball Lifecycle.

  • Numbers of topics : 1858
  • Numbers of messages : 8714
  • Numbers of users : 3801
  • Numbers of points : 1672
Similar topics
ETL from Oracle to SQL Server 2008 Data Warehouse
Hello, Our data warehouse runs on SQL 2008 servers. One of the transactions systems we have runs on an Oracle database and managed by a separate team. What are the recommended methods to extract source data from an Oracle database and loading to a
SQL Server 2008 Date data type as dimension key
We are getting ready to migrate from Microsoft SQL Server 2005 to 2008. Currently we use an integer (in YYYYMMDD format) as the SK on our date dimension table. I am very tempted to start using the new 3-byte Date data type (which stores only the date
Data Warehouse - Indexes
Hi, I am currently at the point where I need to think about Indexes on my data warehouse. We are currently using SQL Server 2005. As a general rule of thumb would the following hold true (Please note that the reporting requirements are still
Dimension Table Indexing Strategy
Please tell me what kind of indexes you are using in your dimension tables in your organization. I am looking for dimension tables indexing strategy for Sybase, Oracle and Db2. If you have any indexing strategy document for Dimension tables for
Fact Table Indexing Strategy
Please explain the indexing strategy which is in use in your organisation for fact tables in your current database(oracle, sybase, db2) Specify volume as the indexing strategy may be based upon the volume of data. Is there a well laid out strategy
Forums from same category
See also
more_less
Informations

0 Replies For the topic :
"SQL Server 2008, page compression and indexing"

This topic has been viewed 1840 times.

Last message :
17/12/2010 at 17h18 by "Jeff Smith"