Take the 2-minute tour ×  I'm creating a sliding window loading
scenario and the partition functions will be changing their
boundaries through time.  I have created some partition
functions in my SQL Server Data Tools (SSDT) database project
with some initial boundaries hardcoded.  However, as time goes
on and the partition functions' boundaries change, future SSDT
database publishes will revert the boundaries to the original
ones.  Is there some way to handle this scenario gracefully,
possibly by disabling the publishing of the partition functions?
I've tried changing the Build Action property of the partition
functions in SSDT, from the default Build, to None, but then the
project fails to build due to a missing reference in the
depending objects.  share|improve this question I always said
that diff based deployment is fundamentally broken. Migrations
is such a vastly superior deployment metaphor! –  Remus Rusanu
Jun 4 '12 at 17:56 add comment  2 Answers  up vote 6 down vote
accepted  I was able to find a