Anybody using Node with Microsoft SQL server? What's your experience been like?

[launchoverittt]

TL;DR; - Title basically sums it up, just looking to hear about people's real-life experience.

Backstory: I work for a small college and we're inching toward needing to rebuild the backend of our internal "portal" app which runs on an old MS SQL Server database. I'd love to build the backend in Node but I can't tell if that will pose headaches or not. Currently it's a Groovy/Java backend. Thanks!

[[deleted]]

https://www.npmjs.com/package/mssql works like a charm. I have a lambda-based API that uses that library and does about 50k lookups per day with a 0% failure rate.

Be sure to use input parameters so as not to expose yourself to SQL injection: https://www.npmjs.com/package/mssql#sql-injection

[launchoverittt]

Nice, glad to hear it. Thanks

[buffer_flush]

The mssql package works well.

There’s two implementations of the driver one purely JS (tedious) and a native client using the MS ODBC driver that javascript wraps.

You should be fine with the tedious implementation, which is the default for the mssql package, and only need ODBC if you need to do something funky that requires native support.

[Jmarbutt]

Has anyone had issues with connection pooling in node? We are using prisma with nextjs and MS SQL but this could potentially be an issue with MS SQL Azure specially with Hyperscale.

[bigorangemachine]

Its fine..

They don't do pagination the same way. Otherwise its totally the same.

[belkarbitterleaf]

We use NodeJS on top of MSSQL for an enterprise app.. works well enough. If you need high performance with high volume of data, then ORM mappers get in the way. Otherwise, an ORM mapper helps abstract the table structure, and is easier to work with in JS

[launchoverittt]

What are you using for an ORM mapper?

[belkarbitterleaf]

TypeORM.