SQL Server 2019 (and 2022)

Integrator.io
,
1

I was attempting to connect to SQL Server 2019, but that option does not exist. I found this post from May 2021 that states:

Celigo's developers are currently revising the connector to explicitly support SQL Server 2019

But four years later the option does not yet exist (nor does 2022). The statement also says that you can use 2017, but my experience disagrees as Celigo spits out:

routines:ssl3_get_record:wrong version number

Is there any timeline as to when newer versions of SQL Server will be supported? Am I doing something wrong to the point that SS17 does not work for my SS19 project or has that backwards compatibility been removed? [I did try all versions with the same error received.] Thank you in advance.

2

The reason selecting 2017 should work is because we currently use version 18.2.4 of the tedious node js repo, which is itself built off of Microsoft's TDS protocol. SQL Server version 2017 points to the Microsoft TDS protocol version 7.4, which supports SQL Server versions 2012/2014/2016/2017/2019/2022. Also, we have internally used 2019 and 2022 AWS RDS databases with the connector so it must be something else. So that being said, I did ask AI to help troubleshoot. Maybe you could try some of these options?

  1. SQL Server Configuration

    • Is Force Encryption enabled on the server?
      Check in SQL Server Configuration Manager → SQL Server Network Configuration → Protocols → TCP/IP → Properties → Certificate / Flags.
    • Is a valid certificate installed?

  2. Port Configuration

    • If you're using port 1433, ensure the SQL Server is configured to accept encrypted connections on that port.
    • If SQL Server is using a different port for SSL, ensure you're using that port.

  3. Tedious Connection Options

    • In your connection config, look for (you can find these in the advanced settings of the connection):

      options: {
    encrypt: true, // If the server doesn't support it, this will cause errors
    trustServerCertificate: true // Bypass validation for dev/test certs
}

      Try setting encrypt: false to test if that's the root cause.

3

My responses below relate to how I am able to connect in SSMS:

  1. No; when Encryption is set to Mandatory my connection fails. My settings that work in SSMS are Force Encryption=Optional and Trust Server Certificate=True.
  2. I am using a different port in SSMS and Celigo [FWIW, if i leave it on port 1443, my error becomes Connection lost - read ECONNRESET]
  3. I have set the Advanced - Configure properties:
    encrypt: false (and tested with true as well)
    trustServerCertificate: true

Version info:

Microsoft SQL Server 2019 (RTM-CU29-GDR) (KB5046860) - 15.0.4410.1 (X64)
Oct 23 2024 15:50:49
Copyright (C) 2019 Microsoft Corporation
Standard Edition (64-bit) on Windows Server 2019 Standard 10.0 (Build 17763: ) (Hypervisor)

4

I would suggest opening a ticket then so support and engineering can troubleshoot.