Also
"Driver={SQL Server Native Client 11.0};Server=(local);Database=AdventureWorks2012;Trusted_Connection={Yes}";
{server: 'localhost', database: 'AdventureWorks2012', trusted: true}Presumably because it links to some native client dll which is built for Windows?
I could be wrong but it doesn't look like a licensing restriction - it's more of a technical limitation.
In my opinion it was very lazy for them to not alter it in this use case. It doesn't make much sense.
That means that you don't have to update the node driver code as well as SQL client if they change the connection string capabilities or SQL client version on the PC.
> The Microsoft Driver for Node.JS for SQL Server is hosted on Github, accentuating our continued involvement with the Open Source community.
Except, this isn't so much openness as it is an underhanded attempt at migrating more developers to their proprietary platforms. It certainly makes business sense for them and I'm not going to make any normative claims, but I wish they wouldn't beat around the bush. The "Open Source" community that they're trying to cater to is more bullshit-averse than they seem to realize.
Shame on them. They shouldn't be contributing software at all if it won't work on every platform. For all they know, I might want to connect to SQL Server from Node.JS running on my Commodore 64, but they don't provide the native code compiled for the 6510.
There are a whole bunch of places with mixed environment where this is extremely useful and can get Node.js approved for use by management who don't want to deal with the headaches of managing, hosting, securing and administering yet another database server like MySQL or PostgreSQL when they already do that for SQL Server and want to run Node on Windows to avoid having to deal with another OS like Linux.
>Except, this isn't so much openness as it is an underhanded attempt at migrating more developers to their proprietary platforms
In these cases, aren't they helping Node get a toe in the door which can lead to further Open Source usage(which in some cases can lead to ditching of SQL Server and going to MySQL or PostgreSQL to save on licensing)?
>but I wish they wouldn't beat around the bush. The "Open Source" community that they're trying to cater to is more bullshit-averse than they seem to realize.
Your comment comes off as incredibly short sighted and negative. If it doesn't work for you, just move on. Where's the beating around the bush? I don't see any claims on the linked blog that they're doing this for openness. Slagging on them for making things more compatible doesn't make sense. If they make it compatible with Linux, some people will say "they're trying to sell their stuff on Linux, it's on FOSS". I think some people will only be happy with open sourcing SQL Server and making it absolutely free which will make them lose 95% of their revenue and I am glad Microsoft is not looking at catering to RMS.
The big deal about all of this is that Node.js can now connect to SQL Server, through a Microsoft developed module. For anyone working at a company that is a Microsoft-based shop (like myself), this is big step to getting to use Node.js at work.
Regarding being Windows only, if an enterprise is running SQL Server, they are probably running Windows enterprise wide, or have at lease a couple application servers running windows. I don't think it is that harsh of a limitation.
Cheers,
It does look rather gnarly but if you work with it for a bit, you will find that connection strings are incredibly powerful.
[Disclaimer: I'm the author.]
It's not native SQL server, but does the job.
Please feel free to let us know what you believe is a good approach!
https://github.com/WindowsAzure/node-sqlserver/issues/17
Thanks,
Jonathan @kop48