Comments
Sort by recent activity
We've been battling with Partition Schemes / Functions and how to deal with them for some time! We've seen this error at times (most recently when a development database was moved to a new server and connected back to the same Git repo!) and come across other issues when deploying them too. We've tried excluding them with the relevant ignore option and excluding them with a filter but always come up against a problem at some point What we're currently doing (just started yesterday so not sure it addresses all our issues yet):
create a new Git repo;
add a Pre-Deployment script with create statements (within existence checks) for all Partition Schemes / Functions;
add Partition Schemes / Functions and tables which use them to the Git repo;
specifically exclude Partition Schemes / Functions from our Azure DevOps Build and Releases using the ifg SQL Compare option.
This means the Partition Schemes / Functions will be created once on every database we deploy to but also covers the issue we see of that "not found" message. / comments
We've been battling with Partition Schemes / Functions and how to deal with them for some time! We've seen this error at times (most recently when a development database was moved to a new server a...