How can we help you today? How can we help you today?

OPTIMIZE_FOR_SEQUENTIAL_KEY not being found?

SQL Compare states that it fully supports SQL 2019, but when I have an index that uses OPTIMIZE_FOR_SEQUENTIAL_KEY=True, it is not generated in any of the scripts, so doesn't show as a difference.   has this been addressed in later versions?  I am currently on 14.2.16.16006.
DAHay
0

Comments

4 comments

Sort by
  • Jon_Kirkwood

    Hi @DAHay

     Thank you for reaching out on the Redgate forums regarding your SQL Compare inquiry.

    Unfortunately functionality around the OPTIMIZE_FOR_SEQUENTIAL_KEY is not yet implemented into the Compare engines that function in SQL Compare & SQL Data Compare.

     

    I have escalated this gap in the software to our development team who have advised they have added it into their backlog and will include it in their next planning meeting. 

     

    At this point I do not have an ETA on when it will be implemented but will endeavor to update this forum post as I receive information.

    Otherwise I would suggest bookmarking the SQL Compare updates page for releases from v14.8.9 onwards that mention this added functionality.

    https://documentation.red-gate.com/sc/release-notes-and-other-versions/sql-compare-14-8-release-notes

     

    We appreciate your report on this missing feature for SQL Server 2019 and look forward to having it implemented in a future release.

    Jon_Kirkwood
    0
  • Jon_Kirkwood
    Checking in on this one - the dev team have moved this from their backlog into active work. 
    No release date to confirm just yet - but wanting to update that there is some movement happening behind the scenes.
    Looking forward to a more definitive update with a future post.
    Jon_Kirkwood
    0
  • DAHay
    Thanks for the follow up, much appreciated!
    DAHay
    0
  • Jon_Kirkwood

    Hi @DAHay

     Thank you for your patience as the team worked on this - I can confirm that a fix has been included with release v14.9.3

     I've run a compare against two tables with optimize_for_sequential_key as a variance and it does now appear as a recognized difference.

     

    Are you able to patch into v14.9.3 at your earliest convenience to verify this has been resolved for you

    Download link here: https://download.red-gate.com/checkforupdates/SQLCompare/SQLCompare_14.9.3.21711.exe 

    Jon_Kirkwood
    0

Add comment

Please sign in to leave a comment.