locked
Known issues in database level when MSSQL Server database upgradation from MSSQL 2008 to MSSQL 2017 RRS feed

  • Question

  • What are known error/issues from SQL Server 2008 to SQL Server 2017 version up gradation at procedure/database object level to comply/fix/recode at application level.

     

    Also, I need to know whether my current environment (SQL Server 2008) procedures, functions, trigger, jobs scripts will be compatible with SQL Server 2017 or if not, what part/features need to be rewritten?


    It will be great if anyone can provide any Microsoft Reference.
    Sunday, March 24, 2019 11:08 AM

All replies

  • Hi Rony,

     

    >>What are known error/issues from SQL Server 2008 to SQL Server 2017 version up gradation at procedure/database object level to comply/fix/recode at application level.

     

     

    The following link contains the problem that users need to improve when using sql server https://feedback.azure.com/forums/908035-sql-server

     

    This unofficial build chart lists all of the known Service Packs (SP), Cumulative Updates (CU) and the problems they fixed: https://sqlserverbuilds.blogspot.com/

     

    >>I need to know whether my current environment (SQL Server 2008) procedures, functions, trigger, jobs scripts will be compatible with SQL Server 2017 or if not, what part/features need to be rewritten?

     

    You can change the compatibility level by making your database compatible with SQL Server2017 related features. The act of changing the compatibility level tells the database to change its feature set. That is, some features will be added, but at the same time some old features will be removed. For more details,please refer to Understanding SQL Server Compatibility Levels and

    ALTER DATABASE (Transact-SQL) Compatibility Level

     

    Hope this could help you .

    Best regards,

    Dedmon Dai


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Monday, March 25, 2019 7:00 AM
  • be compatible with SQL Server 2017 or if not, what part/features need to be rewritten?

    Hello Rony,

    Use the DMA = "Data Migration Assistant" to validate your databases: Perform a SQL Server migration assessment with Data Migration Assistant

    Download at Microsoft® Data Migration Assistant v4.2


    Olaf Helper

    [ Blog] [ Xing] [ MVP]

    Monday, March 25, 2019 4:46 PM