Skip to content

Recommendation for Global Connection in Web Server #164

@cdeutsch

Description

@cdeutsch

Is it better to create one global connection for the life of a web server, for example:

sql.connect(config, function(err) {
  if (err) { console.log('Connect err: ' + err); return; }
  isConnected = true;
});

exports.getLocations = function(callback) {
  var request = new sql.Request();
  request.query('select * from Locations', function(err, recordset) {
    if (err) { callback(err, null); return; }
    callback(null, recordset);
    return;
  });
}

exports.getInstruments = function(callback) {
  var request = new sql.Request();
  request.query('select top 100 * from InstrumentsTLC', function(err, recordset) {
    if (err) { callback(err, null); return; }
    callback(null, recordset);
    return;
  });
}

Or should each request be wrapped in its own connection, for example:

exports.getLocations = function(callback) {
  sql.connect(config, function(err) {
    if (err) { callback(err, null); return; }

    var request = new sql.Request();
    request.query('select * from Locations', function(err, recordset) {
      if (err) { callback(err, null); return; }
      callback(null, recordset);
      return;
    });
  });
}

exports.getInstruments = function(callback) {
  sql.connect(config, function(err) {
    if (err) { callback(err, null); return; }

    var request = new sql.Request();
    request.query('select top 100 * from InstrumentsTLC', function(err, recordset) {
      if (err) { callback(err, null); return; }
      callback(null, recordset);
      return;
    });
  });
}

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions