|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: 2 days ago @ 2:14 PM
Points: 2,414,
Visits: 2,680
|
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Monday, December 10, 2012 7:35 AM
Points: 1,
Visits: 49
|
|
| Just looking and running this script you need to add a DISTINCT to the select it returns multiple duplicate statements for both ALTER TABLE and ALTER INDEX statements
|
|
|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: Monday, June 10, 2013 8:14 AM
Points: 961,
Visits: 797
|
|
You could improve upon this script by using sys.partitions to only include rebuild statements for tables that are already uncompressed. This script will rebuild all tables, regardless of whether or not they are already compressed.
/* ----------------------------- */ Tochter aus Elysium, Wir betreten feuertrunken, Himmlische, dein Heiligtum!
|
|
|
|
|
Valued Member
      
Group: General Forum Members
Last Login: Thursday, February 02, 2012 10:24 PM
Points: 56,
Visits: 195
|
|
| After using row/page/index compression in SQL 2008 DB, I noticed that DB size is increased. Before compression the DB size was 69 GB. After row compression on all tables, size increased to 73GB. Please explain.
|
|
|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: Monday, June 10, 2013 8:14 AM
Points: 961,
Visits: 797
|
|
Soorya (1/15/2012) After using row/page/index compression in SQL 2008 DB, I noticed that DB size is increased. Before compression the DB size was 69 GB. After row compression on all tables, size increased to 73GB. Please explain.
Check in the GUI to make sure that they are compressed. Then check that compression will compress. Compression does not always lead to data savings, especially row compression. It's very dependent on the data that is being compressed.
/* ----------------------------- */ Tochter aus Elysium, Wir betreten feuertrunken, Himmlische, dein Heiligtum!
|
|
|
|