Introducing the Microsoft Driver for Node.JS for SQL Server

"access from any Node.JS applications"....running on Windows. Pretty big limitation which suggests it's business as usual at Microsoft.<p>Also<p><pre><code> "Driver={SQL Server Native Client 11.0};Server=(local);Database=AdventureWorks2012;Trusted_Connection={Yes}"; </code></pre> really should be:<p><pre><code> {server: 'localhost', database: 'AdventureWorks2012', trusted: true}</code></pre>

I'm starting to like the new Microsoft.

For those on *nix, there is this: <a href="https://github.com/w1nk/node-odbc" rel="nofollow">https://github.com/w1nk/node-odbc</a><p>It's not native SQL server, but does the job.

I don't write for Node nor SQL Server, but that connection string looks gnarly. Is there a reason for not using a plain object that could then be merged with a set of internal defaults, then serialized from there? Ruby uses this pattern often, it's very clean and idiomatic.

I was expecting to see that someone ported jTDS (<a href="http://jtds.sourceforge.net/" rel="nofollow">http://jtds.sourceforge.net/</a>) to JavaScript. I have zero idea if something like Emscripten could be used for an effort like that, nor if it would be performant enough for use in a database scenario, but I think a pure JavaScript library would probably be useful to a wider audience.

I've opened an issue to discuss the options for the connection object/array.<p>Please feel free to let us know what you believe is a good approach!<p><a href="https://github.com/WindowsAzure/node-sqlserver/issues/17" rel="nofollow">https://github.com/WindowsAzure/node-sqlserver/issues/17</a><p>Thanks,<p>Jonathan @kop48