1

No Client Protocols or Alias has anything under. Please see attached pic.

missing

Thom A
  • 88,727
  • 11
  • 45
  • 75
  • 3
    SNAC11 was removed from SQL Server 2022. – Dai Apr 25 '23 at 00:45
  • Also: https://dba.stackexchange.com/questions/319901/how-to-create-alias-in-sql-server-2022 – Dai Apr 25 '23 at 00:45
  • SNAC11 also doesn't support versions of SQL Server after 2014. – Thom A Apr 25 '23 at 08:18
  • @ThomA Eh? I'm able to use SNAC11 in a .NET Fx 4.8 program and SSMS18 to connect to my SQL Server 2022 box just fine. – Dai Apr 25 '23 at 21:38
  • Doesn't support doesn't mean doesn't work, @Dai . – Thom A Apr 25 '23 at 21:39
  • @ThomA Okay now we're debating semantics :) – Dai Apr 25 '23 at 21:41
  • But that's the point. If you were to use SSMS 18 to try and design a table on your 2022 instance, for example, *then* you start getting errors. The lack of support *can* mean that only some things don't work, or may not work as expected, @Dai . – Thom A Apr 25 '23 at 21:47

1 Answers1

0

Like @Dai said, it was removed from SQL Server 2022.

As described e. g. here https://learn.microsoft.com/en-us/system-center/dpm/install-dpm?view=sc-dpm-2022 , one can manually install the 2012 runtime and will also see the client protocols on SQL Server 2022. The download can be found at https://www.microsoft.com/en-us/download/details.aspx?id=50402 . Though it did not prompt for restart, it only was visible and working properly after restart (half visible + working before restart). Though Dai already said the same just without the link.

Andreas Reiff
  • 7,961
  • 10
  • 50
  • 104