|
|
|
SSCommitted
Group: General Forum Members
Last Login: Yesterday @ 12:35 PM
Points: 1,715,
Visits: 5,099
|
|
|
|
|
|
Forum Newbie
Group: General Forum Members
Last Login: Thursday, January 08, 2009 11:14 AM
Points: 2,
Visits: 4
|
|
| Thank you for your article. I'd like to know if anyone uses synonyms that point to a different database. I was thinking about moving all of my 'Fact' tables from the general database into a separate database and creating synonyms that point from the general database to the tables in the 'Fact' database. My rationale for this is that I could easily separate and manage the 'Master' tables from the 'Fact' tables and then I could set up the 'Fact' database with compression and leave the general database intact. Has anyone else done anything like this and if so what were your results?
|
|
|
|
|
SSCertifiable
Group: General Forum Members
Last Login: Yesterday @ 11:24 AM
Points: 6,144,
Visits: 1,568
|
|
compression works at the "table" level why would you care to move it out of the database?
* Noel
|
|
|
|
|
Forum Newbie
Group: General Forum Members
Last Login: Thursday, January 08, 2009 11:14 AM
Points: 2,
Visits: 4
|
|
| Good point. I was thinking it was at the database level. I have other reasons for moving it into a separate database but it appears that compression is irrelevant. Thanks.
|
|
|
|
|
SSChampion
Group: Administrators
Last Login: Yesterday @ 4:30 PM
Points: 21,860,
Visits: 6,079
|
|
It doesn't make sense to move fact tables out. As mentioned above, compression works at the table level, and also at the index level. You can compress a table and not the indexes, or vice versa, or compress both.
|
|
|
|
|
SSC-Enthusiastic
Group: General Forum Members
Last Login: Tuesday, October 06, 2009 4:09 PM
Points: 109,
Visits: 78
|
|
hm, good .sql, but is biggest, rsrs i'm never look one this...
because i'm amateur, rsrs
|
|
|
|
|
Hall of Fame
Group: General Forum Members
Last Login: 2 days ago @ 4:28 PM
Points: 3,130,
Visits: 2,258
|
|
Good article. It was helpful to know about the allocation units. I am in the process of designing a data mart type application DB where we'll be storing billions of rows in some of our fact tables. I have been looking forward to testing out the performance benefits of data compression. Your timing for this article could not have been better. Thanks for sharing.....
|
|
|
|
|
SSCommitted
Group: General Forum Members
Last Login: Yesterday @ 12:35 PM
Points: 1,715,
Visits: 5,099
|
|
The performance benefits and the space savings. I've always found it difficult to get additional storage on our SAN, so compression gives me a lot more leeway from a time perspective to get the disk space I need.
One of the things I neglected to mention was that compressed tables are still compressed further as a part of the SQL Server 2008 compressed backup (or third party backup solution), so your backups could actually be an order of magnitude than what they are currently. This is especially useful when you need to refresh development or test environments from those backups (provided that your dev and test are running a SQL Server edition that supports compression).
|
|
|
|
|
Hall of Fame
Group: General Forum Members
Last Login: Thursday, November 12, 2009 7:14 AM
Points: 3,295,
Visits: 964
|
|
|
|
|
|
SSC-Enthusiastic
Group: General Forum Members
Last Login: Tuesday, November 10, 2009 11:32 AM
Points: 136,
Visits: 140
|
|
|
|
|
