What is mssql?
The mssql npm package is a Microsoft SQL Server client for Node.js. It allows you to connect to SQL Server databases, execute queries, and manage transactions. It supports both Promises and async/await syntax, making it versatile for different coding styles.
What are mssql's main functionalities?
Connecting to a SQL Server
This code demonstrates how to connect to a SQL Server database using the mssql package. You need to provide your database credentials and server information in the config object.
const sql = require('mssql');
const config = {
user: 'your_username',
password: 'your_password',
server: 'your_server',
database: 'your_database'
};
async function connectToDatabase() {
try {
let pool = await sql.connect(config);
console.log('Connected to the database');
} catch (err) {
console.error('Database connection failed: ', err);
}
}
connectToDatabase();
Executing a Query
This code demonstrates how to execute a SQL query using the mssql package. It connects to the database and runs a SELECT query on a specified table.
const sql = require('mssql');
const config = {
user: 'your_username',
password: 'your_password',
server: 'your_server',
database: 'your_database'
};
async function executeQuery() {
try {
let pool = await sql.connect(config);
let result = await pool.request().query('SELECT * FROM your_table');
console.log(result);
} catch (err) {
console.error('Query execution failed: ', err);
}
}
executeQuery();
Using Prepared Statements
This code demonstrates how to use prepared statements with the mssql package. Prepared statements are useful for executing queries with parameters, which can help prevent SQL injection attacks.
const sql = require('mssql');
const config = {
user: 'your_username',
password: 'your_password',
server: 'your_server',
database: 'your_database'
};
async function executePreparedStatement() {
try {
let pool = await sql.connect(config);
let ps = new sql.PreparedStatement(pool);
ps.input('input_parameter', sql.Int);
await ps.prepare('SELECT * FROM your_table WHERE id = @input_parameter');
let result = await ps.execute({ input_parameter: 1 });
console.log(result);
await ps.unprepare();
} catch (err) {
console.error('Prepared statement execution failed: ', err);
}
}
executePreparedStatement();
Managing Transactions
This code demonstrates how to manage transactions using the mssql package. Transactions allow you to execute a series of queries as a single unit of work, which can be committed or rolled back based on success or failure.
const sql = require('mssql');
const config = {
user: 'your_username',
password: 'your_password',
server: 'your_server',
database: 'your_database'
};
async function manageTransaction() {
try {
let pool = await sql.connect(config);
let transaction = new sql.Transaction(pool);
await transaction.begin();
let request = new sql.Request(transaction);
await request.query('INSERT INTO your_table (column1) VALUES (value1)');
await transaction.commit();
console.log('Transaction committed');
} catch (err) {
console.error('Transaction failed: ', err);
if (transaction) await transaction.rollback();
}
}
manageTransaction();
Other packages similar to mssql
mysql
The mysql package is a client for MySQL databases. It provides similar functionalities to mssql, such as connecting to a database, executing queries, and managing transactions. However, it is specifically designed for MySQL databases.
pg
The pg package is a PostgreSQL client for Node.js. Like mssql, it allows you to connect to a database, execute queries, and manage transactions. It is tailored for PostgreSQL databases and offers features specific to PostgreSQL.
sqlite3
The sqlite3 package is a client for SQLite databases. It provides functionalities for connecting to SQLite databases, executing queries, and managing transactions. Unlike mssql, it is designed for lightweight, file-based databases.
node-mssql
An easy-to-use MSSQL database connector for Node.js.
There are some TDS modules which offer functionality to communicate with MSSQL databases but none of them does offer enough comfort - implementation takes a lot of lines of code. So I decided to create this module, that make work as easy as it could without losing any important functionality. node-mssql uses other TDS modules as drivers and offer easy to use unified interface. It also add extra features and bug fixes.
There is also co wrapper available - co-mssql.
Extra features:
- Unified interface for multiple MSSQL modules
- Connection pooling with Transactions and Prepared statements
- Parametrized Stored Procedures in node-tds and Microsoft Driver for Node.js for SQL Server
- Serialization of Geography and Geometry CLR types
- Injects original TDS modules with enhancements and bug fixes
At the moment it support three TDS modules:
What's new in 0.6.x (stable, npm)
- Updated to latest Tedious 1.0.0
- Added support for Streaming
- Added option to set request timeout (
config.requestTimeout = 15000
)
Installation
npm install mssql
Quick Example
var sql = require('mssql');
var config = {
user: '...',
password: '...',
server: 'localhost',
database: '...',
options: {
encrypt: true
}
}
var connection = new sql.Connection(config, function(err) {
var request = new sql.Request(connection);
request.query('select 1 as number', function(err, recordset) {
console.dir(recordset);
});
var request = new sql.Request(connection);
request.input('input_parameter', sql.Int, 10);
request.output('output_parameter', sql.VarChar(50));
request.execute('procedure_name', function(err, recordsets, returnValue) {
console.dir(recordsets);
});
});
Quick Example with one global connection
var sql = require('mssql');
var config = {
user: '...',
password: '...',
server: 'localhost',
database: '...',
options: {
encrypt: true
}
}
sql.connect(config, function(err) {
var request = new sql.Request();
request.query('select 1 as number', function(err, recordset) {
console.dir(recordset);
});
var request = new sql.Request();
request.input('input_parameter', sql.Int, value);
request.output('output_parameter', sql.VarChar(50));
request.execute('procedure_name', function(err, recordsets, returnValue) {
console.dir(recordsets);
});
});
### Streaming example with one global connection
If you plan to work with large amount of rows, you should always use streaming. Once you enable this, you must listen for events to receive data.
var sql = require('mssql');
var config = {
user: '...',
password: '...',
server: 'localhost',
database: '...',
options: {
encrypt: true
}
}
sql.connect(config, function(err) {
var request = new sql.Request();
request.stream = true;
request.query('select * from verylargetable');
request.on('recordset', function(columns) {
});
request.on('row', function(row) {
});
request.on('error', function(err) {
});
request.on('done', function(returnValue) {
});
});
Documentation
Configuration
Connections
Requests
Transactions
Prepared Statements
Other
Configuration
var config = {
user: '...',
password: '...',
server: 'localhost',
database: '...',
pool: {
max: 10,
min: 0,
idleTimeoutMillis: 30000
}
}
### Basic configuration is same for all drivers.
- driver - Driver to use (default:
tedious
). Possible values: tedious
, msnodesql
or tds
. - user - User name to use for authentication.
- password - Password to use for authentication.
- server - Server to connect to. You can use 'localhost\instance' to connect to named instance.
- port - Port to connect to (default:
1433
). Don't set when connecting to named instance. - database - Database to connect to (default: dependent on server configuration).
- connectionTimeout - Connection timeout in ms (default:
15000
). - requestTimeout - Request timeout in ms (default:
15000
). - stream - Stream recordsets/rows instead of returning them all at once as an argument of callback (default:
false
). You can also enable streaming for each request independently (request.stream = true
). Always set to true
if you plan to work with large amount of rows. - pool.max - The maximum number of connections there can be in the pool (default:
10
). - pool.min - The minimun of connections there can be in the pool (default:
0
). - pool.idleTimeoutMillis - The Number of milliseconds before closing an unused connection (default:
30000
).
### Tedious
- options.instanceName - The instance name to connect to. The SQL Server Browser service must be running on the database server, and UDP port 1444 on the database server must be reachable.
- options.useUTC - A boolean determining whether or not use UTC time for values without time zone offset (default:
true
). - options.encrypt - A boolean determining whether or not the connection will be encrypted (default:
false
) Encryption support is experimental. - options.tdsVersion - The version of TDS to use (default:
7_4
, available: 7_1
, 7_2
, 7_3_A
, 7_3_B
, 7_4
). - options.appName - Application name used for SQL server logging.
More information about Tedious specific options: http://pekim.github.io/tedious/api-connection.html
### Microsoft Driver for Node.js for SQL Server
This driver is not part of the default package and must be installed separately by npm install msnodesql
. If you are looking for compiled binaries, see node-sqlserver-binary.
- options.instanceName - The instance name to connect to. The SQL Server Browser service must be running on the database server, and UDP port 1444 on the database server must be reachable.
- connectionString - Connection string (default: see below).
- options.trustedConnection - Use Windows Authentication (default:
false
). - options.useUTC - A boolean determining whether or not to use UTC time for values without time zone offset (default:
true
).
Default connection string when connecting to port:
Driver={SQL Server Native Client 11.0};Server={#{server},#{port}};Database={#{database}};Uid={#{user}};Pwd={#{password}};Trusted_Connection={#{trusted}};
Default connection string when connecting to named instance:
Driver={SQL Server Native Client 11.0};Server={#{server}\\#{instance}};Database={#{database}};Uid={#{user}};Pwd={#{password}};Trusted_Connection={#{trusted}};
### node-tds
This driver is not part of the default package and must be installed separately by npm install tds
.
This module update node-tds driver with extra features and bug fixes by overriding some of its internal functions. If you want to disable this, require module with var sql = require('mssql/nofix')
.
## Connections
var connection = new sql.Connection({ });
Errors
- EDRIVER (
ConnectionError
) - Unknown driver.
Events
- connect - Dispatched after connection has established.
- close - Dispatched after connection has closed a pool (by calling
close
).
### connect([callback])
Create connection to the server.
Arguments
- callback(err) - A callback which is called after connection has established, or an error has occurred. Optional.
Example
var connection = new sql.Connection({
user: '...',
password: '...',
server: 'localhost',
database: '...'
});
connection.connect(function(err) {
});
Errors
- ELOGIN (
ConnectionError
) - Login failed. - ETIMEOUT (
ConnectionError
) - Connection timeout. - EALREADYCONNECTED (
ConnectionError
) - Database is already connected! - EALREADYCONNECTING (
ConnectionError
) - Already connecting to database! - EINSTLOOKUP (
ConnectionError
) - Instance lookup failed. - ESOCKET (
ConnectionError
) - Socket error.
### close()
Close connection to the server.
Example
connection.close();
## Requests
var request = new sql.Request();
If you omit connection argument, global connection is used instead.
Events
- recordset(columns) - Dispatched when metadata for new recordset are parsed.
- row(row) - Dispatched when new row is parsed.
- done(returnValue) - Dispatched when request is complete.
- error(err) - Dispatched on error.
### execute(procedure, [callback])
Call a stored procedure.
Arguments
- procedure - Name of the stored procedure to be executed.
- callback(err, recordsets, returnValue) - A callback which is called after execution has completed, or an error has occurred.
returnValue
is also accessible as property of recordsets.
Example
var request = new sql.Request();
request.input('input_parameter', sql.Int, value);
request.output('output_parameter', sql.Int);
request.execute('procedure_name', function(err, recordsets, returnValue) {
console.log(recordsets.length);
console.log(recordsets[0].length);
console.log(returnValue);
console.log(recordsets.returnValue);
console.log(request.parameters.output_parameter.value);
});
Errors
- EREQUEST (
RequestError
) - Message from SQL Server - ECANCEL (
RequestError
) - Canceled. - ETIMEOUT (
RequestError
) - Request timeout. - ENOCONN (
RequestError
) - No connection is specified for that request. - ENOTOPEN (
ConnectionError
) - Connection not yet open. - ENOTBEGUN (
TransactionError
) - Transaction has not begun.
### input(name, [type], value)
Add an input parameter to the request.
Arguments
- name - Name of the input parameter without @ char.
- type - SQL data type of input parameter. If you omit type, module automaticaly decide which SQL data type should be used based on JS data type.
- value - Input parameter value.
undefined
ans NaN
values are automatically converted to null
values.
Example
request.input('input_parameter', value);
request.input('input_parameter', sql.Int, value);
JS Data Type To SQL Data Type Map
String
-> sql.NVarChar
Number
-> sql.Int
Boolean
-> sql.Bit
Date
-> sql.DateTime
Buffer
-> sql.VarBinary
sql.Table
-> sql.TVP
Default data type for unknown object is sql.NVarChar
.
You can define your own type map.
sql.map.register(MyClass, sql.Text);
You can also overwrite the default type map.
sql.map.register(Number, sql.BigInt);
Errors
- EARGS (
RequestError
) - Invalid number of arguments.
### output(name, type, [value])
Add an output parameter to the request.
Arguments
- name - Name of the output parameter without @ char.
- type - SQL data type of output parameter.
- value - Output parameter value initial value.
undefined
and NaN
values are automatically converted to null
values. Optional.
Example
request.output('output_parameter', sql.Int);
request.output('output_parameter', sql.VarChar(50), 'abc');
### query(command, [callback])
Execute the SQL command.
Arguments
- command - T-SQL command to be executed.
- callback(err, recordset) - A callback which is called after execution has completed, or an error has occurred.
Example
var request = new sql.Request();
request.query('select 1 as number', function(err, recordset) {
console.log(recordset[0].number);
});
Errors
- ETIMEOUT (
RequestError
) - Request timeout. - EREQUEST (
RequestError
) - Message from SQL Server - ECANCEL (
RequestError
) - Canceled. - ENOCONN (
RequestError
) - No connection is specified for that request. - ENOTOPEN (
ConnectionError
) - Connection not yet open. - ENOTBEGUN (
TransactionError
) - Transaction has not begun.
You can enable multiple recordsets in queries with the request.multiple = true
command.
var request = new sql.Request();
request.multiple = true;
request.query('select 1 as number; select 2 as number', function(err, recordsets) {
console.log(recordsets[0][0].number);
console.log(recordsets[1][0].number);
});
### cancel()
Cancel currently executing request. Return true
if cancellation packet was send successfully. Not available in msnodesql
and tds
drivers.
Example
var request = new sql.Request();
request.query('waitfor delay \'00:00:05\'; select 1 as number', function(err, recordset) {
console.log(err instanceof sql.RequestError);
console.log(err.message);
console.log(err.code);
});
request.cancel();
## Transactions
Important: always use Transaction
class to create transactions - it ensures that all your requests are executed on one connection. Once you call begin
, a single connection is acquired from the connection pool and all subsequent requests (initialized with the Transaction
object) are executed exclusively on this connection. Transaction also contains a queue to make sure your requests are executed in series. After you call commit
or rollback
, connection is then released back to the connection pool.
var transaction = new sql.Transaction();
If you omit connection argument, global connection is used instead.
Example
var transaction = new sql.Transaction();
transaction.begin(function(err) {
var request = new sql.Request(transaction);
request.query('insert into mytable (mycolumn) values (12345)', function(err, recordset) {
transaction.commit(function(err, recordset) {
console.log("Transaction commited.");
});
});
});
Transaction can also be created by var transaction = connection.transaction();
. Requests can also be created by var request = transaction.request();
.
Events
- begin - Dispatched when transaction begin.
- commit - Dispatched on successful commit.
- rollback - Dispatched on successful rollback.
### begin([isolationLevel], [callback])
Begin a transaction.
Arguments
- isolationLevel - Controls the locking and row versioning behavior of TSQL statements issued by a connection. Optional.
READ_COMMITTED
by default. For possible values see sql.ISOLATION_LEVEL
. - callback(err) - A callback which is called after transaction has began, or an error has occurred. Optional.
Example
var transaction = new sql.Transaction();
transaction.begin(function(err) {
});
Errors
- ENOTOPEN (
ConnectionError
) - Connection not yet open. - EALREADYBEGUN (
TransactionError
) - Transaction has already begun.
### commit([callback])
Commit a transaction.
Arguments
- callback(err) - A callback which is called after transaction has committed, or an error has occurred. Optional.
Example
var transaction = new sql.Transaction();
transaction.begin(function(err) {
transaction.commit(function(err) {
})
});
Errors
- ENOTBEGUN (
TransactionError
) - Transaction has not begun. - EREQINPROG (
TransactionError
) - Can't commit transaction. There is a request in progress.
### rollback([callback])
Rollback a transaction.
Arguments
- callback(err) - A callback which is called after transaction has rolled back, or an error has occurred. Optional.
Example
var transaction = new sql.Transaction();
transaction.begin(function(err) {
transaction.rollback(function(err) {
})
});
Errors
- ENOTBEGUN (
TransactionError
) - Transaction has not begun. - EREQINPROG (
TransactionError
) - Can't rollback transaction. There is a request in progress.
## PreparedStatement
Important: always use PreparedStatement
class to create prepared statements - it ensures that all your executions of prepared statement are executed on one connection. Once you call prepare
, a single connection is aquired from the connection pool and all subsequent executions are executed exclusively on this connection. Prepared Statement also contains a queue to make sure your executions are executed in series. After you call unprepare
, the connection is then released back to the connection pool.
var ps = new sql.PreparedStatement();
If you omit the connection argument, the global connection is used instead.
Example
var ps = new sql.PreparedStatement();
ps.input('param', sql.Int);
ps.prepare('select @param as value', function(err) {
ps.execute({param: 12345}, function(err, recordset) {
ps.unprepare(function(err) {
});
});
});
IMPORTANT: Remember that each prepared statement means one reserved connection from the pool. Don't forget to unprepare a prepared statement!
TIP: You can also create prepared statements in transactions (new sql.PreparedStatement(transaction)
), but keep in mind you can't execute other requests in the transaction until you call unprepare
.
### input(name, type)
Add an input parameter to the prepared statement.
Arguments
- name - Name of the input parameter without @ char.
- type - SQL data type of input parameter.
Example
ps.input('input_parameter', sql.Int);
ps.input('input_parameter', sql.VarChar(50));
Errors
- EARGS (
PreparedStatementError
) - Invalid number of arguments.
### output(name, type)
Add an output parameter to the prepared statement.
Arguments
- name - Name of the output parameter without @ char.
- type - SQL data type of output parameter.
Example
ps.output('output_parameter', sql.Int);
ps.output('output_parameter', sql.VarChar(50));
Errors
- EARGS (
PreparedStatementError
) - Invalid number of arguments.
### prepare(statement, [callback])
Prepare a statement.
Arguments
- statement - T-SQL statement to prepare.
- callback(err) - A callback which is called after preparation has completed, or an error has occurred. Optional.
Example
var ps = new sql.PreparedStatement();
ps.prepare('select @param as value', function(err) {
});
Errors
- ENOTOPEN (
ConnectionError
) - Connection not yet open. - EALREADYPREPARED (
PreparedStatementError
) - Statement is already prepared. - ENOTBEGUN (
TransactionError
) - Transaction has not started.
### execute(values, [callback])
Execute a prepared statement.
Arguments
- values - An object whose names correspond to the names of parameters that were added to the prepared statement before it was prepared.
- callback(err) - A callback which is called after execution has completed, or an error has occurred. Optional.
Example
var ps = new sql.PreparedStatement();
ps.input('param', sql.Int);
ps.prepare('select @param as value', function(err) {
ps.execute({param: 12345}, function(err, recordset) {
console.log(recordset[0].value);
})
});
You can enable multiple recordsets by ps.multiple = true
command.
var ps = new sql.PreparedStatement();
ps.input('param', sql.Int);
ps.prepare('select @param as value', function(err) {
ps.multiple = true;
ps.execute({param: 12345}, function(err, recordsets) {
console.log(recordsets[0][0].value);
})
});
Errors
- ENOTPREPARED (
PreparedStatementError
) - Statement is not prepared.
### unprepare([callback])
Unprepare a prepared statement.
Arguments
- callback(err) - A callback which is called after unpreparation has completed, or an error has occurred. Optional.
Example
var ps = new sql.PreparedStatement();
ps.input('param', sql.Int);
ps.prepare('select @param as value', function(err, recordsets) {
ps.unprepare(function(err) {
});
});
Errors
- ENOTPREPARED (
PreparedStatementError
) - Statement is not prepared.
## Geography and Geometry
node-mssql has built-in serializer for Geography and Geometry CLR data types.
select geography::STGeomFromText('LINESTRING(-122.360 47.656, -122.343 47.656 )', 4326)
select geometry::STGeomFromText('LINESTRING (100 100 10.3 12, 20 180, 180 180)', 0)
Results in:
{ srid: 4326,
version: 1,
points: [ { x: 47.656, y: -122.36 }, { x: 47.656, y: -122.343 } ],
figures: [ { attribute: 1, pointOffset: 0 } ],
shapes: [ { parentOffset: -1, figureOffset: 0, type: 2 } ],
segments: [] }
{ srid: 0,
version: 1,
points:
[ { x: 100, y: 100, z: 10.3, m: 12 },
{ x: 20, y: 180, z: NaN, m: NaN },
{ x: 180, y: 180, z: NaN, m: NaN } ],
figures: [ { attribute: 1, pointOffset: 0 } ],
shapes: [ { parentOffset: -1, figureOffset: 0, type: 2 } ],
segments: [] }
## Table-Valued Parameter (TVP)
Supported on SQL Server 2008 and later. You can pass a data table as a parameter to stored procedure. First, we have to create custom type in our database.
CREATE TYPE TestType AS TABLE ( a VARCHAR(50), b INT );
Next we will need a stored procedure.
CREATE PROCEDURE MyCustomStoredProcedure (@tvp TestType readonly) AS SELECT * FROM @tvp
Now let's go back to our Node.js app.
var tvp = new sql.Table()
tvp.columns.add('a', sql.VarChar(50));
tvp.columns.add('b', sql.Int);
tvp.rows.add('hello tvp', 777);
You can send table as a parameter to stored procedure.
var request = new sql.Request();
request.input('tvp', tvp);
request.execute('MyCustomStoredProcedure', function(err, recordsets, returnValue) {
console.dir(recordsets[0][0]);
});
TIP: You can also create Table variable from any recordset with recordset.toTable()
.
## Errors
There are three type of errors you can handle:
- ConnectionError - Errors related to connections and connection pool.
- TransactionError - Errors related to creating, commiting and rolling back transactions.
- RequestError - Errors related to queries and stored procedures execution.
- PreparedStatementError - Errors related to prepared statements.
Those errors are initialized in node-mssql module and its original stack can be cropped. You can always access original error with err.originalError
.
SQL Server may generate more than one error for one request so you can access preceding errors with err.precedingErrors
.
Error Codes
Each known error has code
property.
Type | Code | Description |
---|
ConnectionError | ELOGIN | Login failed. |
ConnectionError | ETIMEOUT | Connection timeout. |
ConnectionError | EDRIVER | Unknown driver. |
ConnectionError | EALREADYCONNECTED | Database is already connected! |
ConnectionError | EALREADYCONNECTING | Already connecting to database! |
ConnectionError | ENOTOPEN | Connection not yet open. |
ConnectionError | EINSTLOOKUP | Instance lookup failed. |
ConnectionError | ESOCKET | Scoket error. |
TransactionError | ENOTBEGUN | Transaction has not begun. |
TransactionError | EALREADYBEGUN | Transaction has already begun. |
TransactionError | EREQINPROG | Can't commit/rollback transaction. There is a request in progress. |
RequestError | EREQUEST | Message from SQL Server |
RequestError | ECANCEL | Canceled. |
RequestError | ETIMEOUT | Request timeout. |
RequestError | EARGS | Invalid number of arguments. |
RequestError | ENOCONN | No connection is specified for that request. |
PreparedStatementError | EARGS | Invalid number of arguments. |
PreparedStatementError | EALREADYPREPARED | Statement is already prepared. |
PreparedStatementError | ENOTPREPARED | Statement is not prepared. |
## Metadata
Recordset metadata are accessible through the recordset.columns
property.
var request = new sql.Request();
request.query('select 1 as first, \'asdf\' as second', function(err, recordset) {
console.dir(recordset.columns);
console.log(recordset.columns.first.type === sql.Int);
console.log(recordset.columns.second.type === sql.VarChar);
});
Columns structure for example above:
{ first: { name: 'first', length: 10, type: [sql.Int] },
second: { name: 'second', length: 4, type: [sql.VarChar] } }
## Data Types
You can define data types with length/precision/scale:
request.input("name", sql.VarChar, "abc");
request.input("name", sql.VarChar(50), "abc");
request.input("name", sql.VarChar(sql.MAX), "abc");
request.output("name", sql.VarChar);
request.output("name", sql.VarChar, "abc");
request.input("name", sql.Decimal, 155.33);
request.input("name", sql.Decimal(10), 155.33);
request.input("name", sql.Decimal(10, 2), 155.33);
request.input("name", sql.DateTime2, new Date());
request.input("name", sql.DateTime2(5), new Date());
List of supported data types:
sql.Bit
sql.BigInt
sql.Decimal ([precision], [scale])
sql.Float
sql.Int
sql.Money
sql.Numeric ([precision], [scale])
sql.SmallInt
sql.SmallMoney
sql.Real
sql.TinyInt
sql.Char ([length])
sql.NChar ([length])
sql.Text
sql.NText
sql.VarChar ([length])
sql.NVarChar ([length])
sql.Xml
sql.Time ([scale])
sql.Date
sql.DateTime
sql.DateTime2 ([scale])
sql.DateTimeOffset ([scale])
sql.SmallDateTime
sql.UniqueIdentifier
sql.Binary
sql.VarBinary ([length])
sql.Image
sql.UDT
sql.Geography
sql.Geometry
To setup MAX length for VarChar
, NVarChar
and VarBinary
use sql.MAX
length.
## Verbose Mode
You can enable verbose mode by request.verbose = true
command.
var request = new sql.Request();
request.verbose = true;
request.input('username', 'patriksimek');
request.input('password', 'dontuseplaintextpassword');
request.input('attempts', 2);
request.execute('my_stored_procedure');
Output for the example above could look similar to this.
---------- sql execute --------
proc: my_stored_procedure
input: @username, varchar, patriksimek
input: @password, varchar, dontuseplaintextpassword
input: @attempts, bigint, 2
---------- response -----------
{ id: 1,
username: 'patriksimek',
password: 'dontuseplaintextpassword',
email: null,
language: 'en',
attempts: 2 }
---------- --------------------
return: 0
duration: 5ms
---------- completed ----------
## Known issues
Tedious
msnodesql
- msnodesql 0.2.1 contains bug in DateTimeOffset (reported)
- msnodesql 0.2.1 doesn't support TVP data type.
- msnodesql 0.2.1 doesn't support request timeout.
node-tds
- If you're facing problems with date, try changing your tsql language
set language 'English';
. - node-tds 0.1.0 doesn't support connecting to named instances.
- node-tds 0.1.0 contains bug and return same value for columns with same name.
- node-tds 0.1.0 doesn't support codepage of input parameters.
- node-tds 0.1.0 contains bug in selects that doesn't return any values (select @param = 'value').
- node-tds 0.1.0 doesn't support Binary, VarBinary and Image as parameters.
- node-tds 0.1.0 always return date/time values in local time.
- node-tds 0.1.0 has serious problems with MAX types.
- node-tds 0.1.0 doesn't support TVP data type.
- node-tds 0.1.0 doesn't support request timeout.
## License
Copyright (c) 2013-2014 Patrik Simek
The MIT License
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.