February 13, 2012 at 10:10 am
Hi,
I thought I heard a PASS in Seattle (October, 2011) that the best practice of keeping SQL Server files out of compressed folders had changed and the performance issues were not as big as first thought.
I am trying to place a MDF file for a test database in a compressed folder and getting an error. Here is the message The file "Y:\MSSQL\Databidw_data.mdf" is compressed but does not reside in a read-only database or filegroup. The file must be decompressed. [SQLSTATE 42000] (Error 62301).
Can it only be done for read-only databases? or is there a SQL Server setting that needs to change to allow it. Anyway around this?
What do people think about this? Has the thinking changed or not?
I am running SQL Server 2008 (not R2) -10-0-5500.
Thanks
Steve
February 13, 2012 at 11:13 am
SQL Server Books online should be able to answer most of your questions.
Read-Only Filegroups and Compression
http://msdn.microsoft.com/en-us/library/ms190257(v=sql.100).aspx
February 13, 2012 at 11:19 am
According to Michael's link, compression (NTFS, not third party) is supported for NDFs only, not MDFs or LDFs.
Quote: Data compression is supported for user data stored in read-only user-defined (.NDF) filegroups. Primary filegroups and transactions logs cannot be compressed unless the database itself is read-only.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply