node-mssql VS MikroORM

Not that often. They're more likely to be c#/java/native places. But there's no barrier really: https://www.npmjs.com/package/mssql

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.

See this package for mssql example https://www.npmjs.com/package/mssql

I have an internal site that I develop that's a node.js server with express, reading from a SQL database. Currently using the mssql package to interact with the db. At different routes within the app, the route handlers read from the database and work their magic and render html. Super basic, there.

Here's a link to a package that allows you to connect Node with MSSQL: https://tediousjs.github.io/node-mssql/

What you can do is use Node.js along with the mssql library to build your site. You can either use templates and render pages on the server, or you can build out an API and write your browser client in a framework like React or Angular.

Microsoft SQL Server https://www.npmjs.com/package/mssql

I am developing an API using nodeJS and Typescript. I was looking for documentation/tutorials (like mssql - npm (npmjs.com) ) to implement a sql server pool with the sql server I have, but there´s a lot of ways to do it and it doesn´t works for me and does not used pool connection, only directly queries, so I will be so glad with you if you can help me. I've been stuck in this 2 days.

In my usual NodeJS tech stack, which includes GraphQL, NestJS, SQL (predominantly PostgreSQL with MikroORM), I encountered these limitations. To overcome them, I've developed a new stack utilizing Rust, which still offers some ease of development:

https://www.npmjs.com/package/mikro-orm - 44 issues

Mikro-ORM is a TypeScript ORM that focuses on simplicity and efficiency. It supports various SQL databases and MongoDB. Mikro-ORM is known for its simplicity and developer-friendly APIs. It provides a concise syntax for defining data models and relationships, making it easy to use.

I found MikroORM [0] to be quite reasonable if you're in the TS ecosystem already. It was also easy to do custom, raw queries, and really just felt like it wasn't in the way.

[0] https://mikro-orm.io/

It also does code generation into its own module, so good luck with hoisting in a monorepo where you want multiple independent prisma schemas. MikroORM[1] is a much better alternative to Prisma in my opinion but any ORM carries some form of baggage.

[1] https://mikro-orm.io/

More about v6 development can be found here.

I recommend looking at https://mikro-orm.io/