Hello,
 Just enabled NTFS compression on a EDB Database and it's working fine ...
 So the question is ... IS IT SAFE ?

Thank you

On 12/25/2018 11:38 AM, Charalampos Michael wrote:
>    Just enabled NTFS compression on a EDB Database and it's working fine ...
>    So the question is ... IS IT SAFE ?

It's OS file system driver level so should be invisible to EDB (or any
other app). Have not used it for DB but use it often for our app logs
folder and never had any issue.

Always have a backup though

Raul

Raul,

> It's OS file system driver level so should be invisible to EDB (or any
> other app). Have not used it for DB but use it often for our app logs
> folder and never had any issue.

Well, i'm stilling wondering why MSSQL Server doesn't allow NTFS compression on their Databases ...

> Always have a backup though

Of course

On 12/29/2018 5:40 AM, Charalampos Michael wrote:
>
> Well, i'm stilling wondering why MSSQL Server doesn't allow NTFS compression on their Databases ...

I'm not up to speed on latest MS-SQL so take rest with grain on salt

Main issues are around recovery and reliability i think :

- SQL database disk recommendation is 64K block size which does not
actually support compression at all

- ntfs does write caching in case of compression being involved which
might be undesirable if one wants the database write to fully flush

- there was something about sector aligned writes and transactional ecovery

- finally there is additional CPU (also of course case with built-in
encryption) and adding another potential point of failure

Raul

Thank Raul! interesting ...

Michael,

<< Well, i'm stilling wondering why MSSQL Server doesn't allow NTFS compression on their Databases ... >>

SQL Server might have an option for raw file I/O, which bypasses the Windows file system (to some degree, at least the caching layer) and this may affect the ability to use NTFS compression with database files in such a scenario.

Tim Young
Elevate Software
www.elevatesoft.com