Some backups don't compress #188
Replies: 10 comments
-
|
Could it be that you have TDE on the database? If the database has TDE you need to be on SQL Server 2016, and also specify MAXTRANSFERSIZE for compression to work. Another reason could be if the database contains data that already is compressed (e.g. images). |
Beta Was this translation helpful? Give feedback.
-
|
Please submit a separate issue for the second question. |
Beta Was this translation helpful? Give feedback.
-
|
No TDE, all SQL Server Standard, no images stored in the databases. |
Beta Was this translation helpful? Give feedback.
-
|
Separate issue #189 submitted as requested. |
Beta Was this translation helpful? Give feedback.
-
|
Could you post the backup command from the output file. Does it include WITH COMPRESSION? |
Beta Was this translation helpful? Give feedback.
-
|
Where do you store the output file, please??
Once I know, I'll look for it.
The checkbox for compression is ticked in the relevant properties window.
The account running the backups has full access to the databases, backups, etc. etc.
|
Beta Was this translation helpful? Give feedback.
-
|
The only thing that you need to do is to add |
Beta Was this translation helpful? Give feedback.
-
|
If you go into Job Step Properties and Advanced, then you can see the location of the output - files. |
Beta Was this translation helpful? Give feedback.
-
|
?OIC!! I will do this tonight!! :)
Thank you for helping me!! :)
|
Beta Was this translation helpful? Give feedback.
-
|
I've done this and compression now works properly.
I also always tick the 'enable compression' box in database properties.
|
Beta Was this translation helpful? Give feedback.
-
Some backups don't compress, can anyone suggest why?? (not all backups, just some, is there anything in these scripts to encourage/ensure compression)
Beta Was this translation helpful? Give feedback.
All reactions