Please add an option to filters.scpf to ignore filestream properties.
LouisSomers
Posts: 24 Bronze 2
In our development databases we never set the filestream property on any column.
On some production servers, our DBA turns filestream on for specific customers that store large blobs.
When we deploy a new version the filestream property gets removed, tables get huge and backup storage shortage alarms start ringing, with all the panic that follows...
It would be great if you could add an option to the .scpf filters format to ignore the filestream property (also for the SqlCompare and SqlSourceControl products).
Currently we need to exclude the whole table (which seems to have failed the last time around, but we're still investigating).
On some production servers, our DBA turns filestream on for specific customers that store large blobs.
When we deploy a new version the filestream property gets removed, tables get huge and backup storage shortage alarms start ringing, with all the panic that follows...
It would be great if you could add an option to the .scpf filters format to ignore the filestream property (also for the SqlCompare and SqlSourceControl products).
Currently we need to exclude the whole table (which seems to have failed the last time around, but we're still investigating).
Best Answers
-
Peter_Laws
Posts: 288 Silver 2
Hello Louis,
Thank you for your query. For your particularly use case, specifically as it's a predictable scenario, my first thought would be creating a post deployment script to check and then restore the filestream property after the migration has run.
Do you think that could work for you?
Regarding it being a selectable ignore property, please could you raise the matter on our User Voice forum?
This enables the developers to see community demand for functionality and aids the selection process.
Thank you and kind regards,
Peter
Redgate Support
-
LouisSomers
Posts: 24 Bronze 2
Thank you @Peter_Laws
I posted a feature request on user voice.
Running a post deployment script would work, but we are looking for ways to speed up deployment rather than slow it down.
The problem with the excluded table in our .scpf file was that it was included again as a dependency.
Disabling dependencies in addition to excluding the table seems to be the best workaround so far.
