Skip to main content

Connecting Nodejs to SQL Server with Knex ORM - Part 1

Normally we connect Nodejs to the databases like SQLite, MongoDB, Postgres etc. In this multiple part post, I am going to show you, how we can connect Nodejs with Microsoft's SQL Server using Knex and run CRUD operations.
1. Installation of required packages
In order to connect Nodejs to SQL Server with Knex, we will need following node packages installation:
i. npm install knex
ii. npm install mssql
Once the packages are installed, we can write the following code to connect:
 //Code to KNEX connection settings.
 var knex = require('knex')({  
  client: 'mssql',  
   connection: {  
    user: 'sa',  
    password: 'pwd',  
    server: 'localhost',  
    database: 'Test'  
   }  
 });  
 //Code to query the Table DEPT
 knex.select("*").from("dept")  
 .then(function (depts){  
   depts.forEach((dept)=>{ //use of Arrow Function  
     console.log({...dept});  
   });  
 }).catch(function(err) {  
 // All the error can be checked in this piece of code  
   console.log(err);  
 }).finally(function() {  
   // To close the connection pool  
   knex.destroy();  
 });  
The above example has two parts. Part one does the connection string settings for Knex to connect to SQL Server. Part two actually runs a Select query to select all the rows from table named "Dept". Once the program runs successfully, the output will be, based on table data.
{ DEPTNO: 10, DNAME: 'ACCOUNTING', LOC: 'NEW YORK' }
{ DEPTNO: 20, DNAME: 'RESEARCH', LOC: 'DALLAS' }
{ DEPTNO: 30, DNAME: 'SALES', LOC: 'CHICAGO' }
{ DEPTNO: 40, DNAME: 'OPERATIONS', LOC: 'BOSTON' }
The select query was able to fetch all 4 records from the table named "Dept" in my SQL Server database. The result will vary based on your data and table.
Happy Coding!. | dhandrohit@gmail.com





Comments

Popular posts from this blog

SQLServer Error: 15404, Could not obtain information about Windows NT group/user Error code 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin)

If we encounter this error "SQLServer Error: 15404, Could not obtain information about Windows NT group/user Error code 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin)" in SQL Server in which the job fails because of the user account related problem, then we need to take the following steps to make it work: a. Go to SQL Server Agent. b. Then select the job which is giving error and not running successfully. c. Then choose properties and in the General Tab, change the owner to "SA" or any account that has the administrative privileges. The problem will be resolved.

MAX pool size reached in ASP.NET

If you are handling large databases and big application(s) that are running on servers in a cluster, then probably this error might have occurred. In an ASP.NET app, we can use connection pooling that helps to share the connection between multiple request(s) rather than creating more connections. The settings relating to connection pool are defined in web.config file. Max pool size reached error in ASP.NET occurs, when the number of connections go beyond the maximum defined limit in Web.config file. Following are the various settings of the Connection Pooling: Name Default Description Connection Lifetime 0 When a connection is returned to the pool, its creation time is compared with the current time, and the connection is destroyed if that time span (in seconds) exceeds the value specified by  Connection Lifetime . This is useful in clustered configurations to force load balancing between a runnin...