This repository is archived and no longer being maintained. If you are looking for a Node.js driver for SQL Server, please check out Tedious.
This driver is a native C driver that uses the Microsoft ODBC driver under the hood. If you are looking for a pure javascript driver with no dependencies please check out Tedious.
The Microsoft Driver for Node.js for SQL Server allows Node.js applications on Microsoft Windows and Microsoft Windows Azure to access Microsoft SQL Server and Microsoft Windows Azure SQL Database.
This is an initial preview release, and is not production ready. We welcome any feedback, fixes and contributions from the community at this very early stage.
The following prerequisites are necessary prior to using the driver:
- Node.js - use node.js version 0.8.x
- Python 2.7
- Visual C++ 2010 Express
Next install the msnodesql driver
-
Download the msnodesql driver by using the command ‘npm install msnodesql’. This will install Microsoft’s NodeJS-SQL driver into your project. You should now have a folder called msnodesql inside node_modules. Note: This will only work with Node 0.8.9. If you had newer versions, you will have to downgrade.
-
Next go to the file explorer and naviage to the the C:\NodeJSSampleProject\node_modules\msnodesql folder and run the executable(.msi file). Note: You will need Visual C++ 2010 Express before you run the executable. This can be downloaded from here.
Included are a few unit tests. They require mocha, async, and assert to be installed via npm. Also, set the variables in test-config.js, then run the tests as follows:
cd test
node runtests.js
We are aware that many features are still not implemented, and are working to update these. Please visit the project on Github to view outstanding issues.
For now, please see the unit tests for usage examples.
If you would like to become an active contributor to this project please follow the instructions provided in the Contribution Guidelines.
The Microsoft Driver for Node.js for SQL Server is licensed under the Apache 2.0 license. See the LICENSE file for more details.