Q. Windows Server 2019 upgrade error

정완 손 1 Reputation point
2022-04-27T07:51:12.213+00:00

I have a question. Help me.

Upgrading server

The in-progress details are: (Windows server 2008 R2 → Windows server 2012 → Windows server 2016 → Windows server 2019)

I have completed until the current Windows server 2016.

When I upgrade from the current Windows server 2016 to the 2019 version, it turns out that I failed as it became 100%.

Please teach me the way.

and

To ask you a further question,

Likewise, we upgraded sql server 2008 to sql server 2019 version, but will the script contents of the procedure be changed?

'uses the old style join syntax which can have poor performance at database compatibility level 90 and higher' This will be displayed.

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,457 questions
Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,371 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,127 questions
SQL Server Migration Assistant
SQL Server Migration Assistant
A Microsoft tool designed to automate database migration to SQL Server from Access, DB2, MySQL, Oracle, and SAP ASE.
494 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Olaf Helper 40,816 Reputation points
    2022-04-27T08:19:29.417+00:00

    'uses the old style join syntax which can have poor performance at database compatibility level 90 and higher'

    Regarding SQL Server and that message.
    "Old style join" is a deprecated feature and not longer supported in version 2019; you have to modify your SQL code.
    See https://learn.microsoft.com/en-us/sql/relational-databases/performance-monitor/sql-server-deprecated-features-object?view=sql-server-ver15
    => Non-ANSI = or = outer join operators

    0 comments No comments

  2. Dave Patrick 426.1K Reputation points MVP
    2022-04-27T14:25:32.107+00:00

    The much cleaner / safer / less problematic method is to stand up a new 2019, patch fully, then migrate the roles / applications over to it. You can also review the log files here.
    https://learn.microsoft.com/en-us/windows/deployment/upgrade/log-files.

    --please don't forget to upvote and Accept as answer if the reply is helpful--