mShan0

HI @akc42, the warning message is related to #1361. Currently, the `config.options.trustServerCertificate` option defaults to `true`, but is going to be changed to `false` in the future. If you explicitly...

I agree that tedious probably should skip the deprecation warning in your scenario. Given the ease of modifying the config file to include the option to get rid of the...

Hi @Maferamirezz, are you still having this issue? Can you double check that your server and port parameters in the config are correct? Can you also double check that the...

Tedious logs which cipher is being used for the TLS negotiation through the debug output. Can you add something like this to your custom script and run it using Node...

This may be an issue with Node 18 defaulting to TLS 1.3 which is not yet supported by Tedious. The latest version of Tedious makes the default version TLS 1.2....

Hi @YoricWatterott, can you try setting your server to simply localhost? I.e. `server:"localhost"`. Tedious doesn't support the \ format. Can you also double check that your database is configured to...

Hi @Julia1205, based on you getting a 233 error ([Microsoft doc explaining what that is here](https://learn.microsoft.com/en-us/sql/relational-databases/errors-events/mssqlserver-233-database-engine-error?view=sql-server-ver16)), it may be that your database is not configured to accept remote connections. You...

Hi @digitalBush, thanks for the suggestion. We'll take a look into this.

Hi @benjamin-atlas, thanks for bringing the dead links up. The Docs team has been changing up that page. In https://www.microsoft.com/en-us/sql-server/developer-tools/, under "Developing with SQL Server" > "Node.js", it redirects to...

Hi @rgare-jeffa, not sure if this is possible, but will take a look into it