SSC claims partition function is different...but it's not.

SQL Source Control is claiming that my partition function is not the same has that in TFS. However, if I try and check in the 'changes' I get 'CheckIn returned with ChangeSet ID=0, nothing to Check in? Didn't expect 0 actual 0'.

SQL Compare does not report a difference between TFS & the database.

I wouldn't care, but when using DLM Automation in TFS to deploy the change, it claims 'Altering partition functions', but then 'Post-update schema check failed: the schema in the Database Release object (created at 11/04/2018 12:23:18 +01:00) and database 'CMS_Staging' on server '' are different, or static data is different.' and the deployment fails.

So some parts of the SQL Compare engine think there is a difference, but other parts don't Anyone got any suggestions?


  • pcousinspcousins Posts: 9 Bronze 1

    Here's the script for the partition function:

    CREATE PARTITION FUNCTION [pfYearly](DATETIME2(0)) AS RANGE RIGHT FOR VALUES (N'2016-01-01T00:00:00.000', N'2017-01-01T00:00:00.000', N'2018-01-01T00:00:00.000', N'2019-01-01T00:00:00.000', N'2020-01-01T00:00:00.000', N'2021-01-01T00:00:00.000', N'2022-01-01T00:00:00.000')

  • pcousinspcousins Posts: 9 Bronze 1
    This issue is still ongoing, but now SQL Source Code Control errors with 'Failed to locate the partition function [pfYearly] for the [psYearly] partition scheme.
Sign In or Register to comment.