3 ms·

> So like, all of them? Hahahaha I really think that's unfair, untrue even. I work with a lot of services on a regular basis, and while it very frustrating to

> So like, all of them? Hahahaha I really think that's unfair, untrue even. I work with a lot of services on a regular basis, and while it very frustrating to find something with missing documentation, it seems to be confined to certain services, and mostly then for new'ish features. In those cases, they are quite responsive on GitHub. > Next to Azure, this is the next biggest cause of issues at work for me, and I haven't seen any wild advantage of this over Postgres, with the disadvantage that pretty much every linux/macOS and open source tool I use is much happier to plug in to Postgres instead. I also personally prefer Postgres, and by a margin. But I have also worked with SQL Server on Linux, and haven't found any differences over SQL Server on Windows - it just works.

FridgeSeal 6y ago
> I really think that's unfair, untrue even. I work with a lot of services on a regular basis, and while it very frustrating to find something with missing documentation, it seems to be confined to certain services, and mostly then for new'ish features. In those cases, they are quite responsive on GitHub. I was being a bit tongue-in-cheek here, but that is good to know they're responsive on GitHub. > But I have also worked with SQL Server on Linux, and haven't found any differences over SQL Server on Windows - it just works. Sorry I meant SQL Server in general, not specifically the linux one. You're pretty much relegated to using ODBC and messing around with all the requisite configs there, which is fine once it's working, but it's never as nice and straightforward as other db's ime.
- tracker1 6y ago
  > Sorry I meant SQL Server in general, not specifically the linux one. You're pretty much relegated to using ODBC and messing around with all the requisite configs there, which is fine once it's working, but it's never as nice and straightforward as other db's ime. So never dealth with Oracle outside Java? I can't speak too broadly but mssql/tedious modules for node don't use the ODBC interface and work pretty well regardless of platform with minimal issues. My biggest issues with MS SQL Server for Linux vs Windows comes down to some of the features that most dbms don't necessarily support in the first place.

FridgeSeal 6y ago

> I really think that's unfair, untrue even. I work with a lot of services on a regular basis, and while it very frustrating to find something with missing documentation, it seems to be confined to certain services, and mostly then for new'ish features. In those cases, they are quite responsive on GitHub. I was being a bit tongue-in-cheek here, but that is good to know they're responsive on GitHub. > But I have also worked with SQL Server on Linux, and haven't found any differences over SQL Server on Windows - it just works. Sorry I meant SQL Server in general, not specifically the linux one. You're pretty much relegated to using ODBC and messing around with all the requisite configs there, which is fine once it's working, but it's never as nice and straightforward as other db's ime.

tracker1 6y ago
> Sorry I meant SQL Server in general, not specifically the linux one. You're pretty much relegated to using ODBC and messing around with all the requisite configs there, which is fine once it's working, but it's never as nice and straightforward as other db's ime. So never dealth with Oracle outside Java? I can't speak too broadly but mssql/tedious modules for node don't use the ODBC interface and work pretty well regardless of platform with minimal issues. My biggest issues with MS SQL Server for Linux vs Windows comes down to some of the features that most dbms don't necessarily support in the first place.