7 ms·
Be able to use the 1000s of commercial products that need MSSQL. Encryption is easier to manage and it has built in solutions for HIPPA and PCI. SQL reporting
by dogma1138 10y ago
Be able to use the 1000s of commercial products that need MSSQL.
Encryption is easier to manage and it has built in solutions for HIPPA and PCI.
SQL reporting services and the entire ecosystem of apps that run on top of MSSQL..
Better clustering, ha, revision control and backup.
Most likely better enterprise support, and you'll be able to port "legacy" applications that were designed with win/sql in mind without having to rewrite your entire DB access and query code.
- rokosbasilisk 10y agoWouldnt it be easier just to run sql server on windows at that point to take advantage of the ms ecosystem ? Edit: I am not familar with much of anything microsoft related.
- UnoriginalGuy 10y agoYou'd never run MS SQL Server and these other servers on the same machine either way, so you could easily run SQL Server on Linux and Reporting Services on Windows Server. Although if you're virtualizing Windows Server, it may be effectively free to run an additional Windows Server instance (since you pay per core regardless); but if your hypervisor's resources are already saturated then you could take SQL Server off of it and put it onto a inexpensive Linux Server.
- Deinumite 10y agoMaybe but this also gives you more hosting options if you are in the cloud. Also tools like puppet and chef for example have an easier time provisioning Unix like machines than Windows (although this has been changing, and the situation could be much better I haven't dealt with it for a bit). Also you don't have to deal with licenses for Windows server instances which can be another huge painpoint.
- dogma1138 10y agoThere are quite a few products that require a Linux host for the main app server and a MSSQL or Oracle DB. Oracle support is being dropped left and right MSSQL is there because it was the defacto enterprise DB for ages and it also has a free version via MSSQL express. And lastly having more options is never a bad thing.
- statictype 10y agoThere are quite a few products that require a Linux host for the main app server and a MSSQL or Oracle DB. Are there? I'm genuinely curious about what these products, are that run on Linux and use SQL Server.
- dogma1138 10y agoI should've used the require just for the 2nd part just off top on my head a lot of IBM products (e.g. Lotus) can be installed on Linux and only run on MSSQL or Oracle with and ODBC connector rather than their DB2 internal DB.
- ams6110 10y agoOracle support is being dropped left and right By whom? I think "big" enterprise software (SAP, Peoplesoft, etc.) has and will support Oracle for a long time. Many of their customers have huge investments in Oracle, not only financial but training and institutional knowledge.
- krakensden 10y agoIt is hard to run Windows Server in the style favored by serious devops shops- CI for infrastructure, totally automated bring up, etc. There are lots of companies that don't/won't run SQL Server because they don't think they can do that with windows, or don't want to try and port their tooling.
- spydum 10y agoExactly this.. The about shops that have all their server tooling for Linux, and want this nice 3rd party tool but it requires SQL Server.. Either team grins and bears supporting a one off OS and application, or they find another solution and MSFT loses a license.
- dogma1138 10y agoIt's really not, it's that most devops engineers don't want to learn or even bother and most windows sysadmins simply don't know how. Windows automation kinda died when system admins stopped needing to know how to work with JET DB when needing to do one serious ad work. I don't can't think of a single CI or automation thing that works with Linux that you can't do in Windows if pushed I can probably come with considerably more things which are opposite. Licensing is the only thing really that makes windows machines a pain to work with unless you are big enough for a sell reporting volume licensing scheme.
- inferiorhuman 10y agoMy experience at a largely Windows based Fortune 1000 company was that Windows is that hard. I dealt with 12-ish factor apps on Linux exclusively, but the teams dealing with legacy stuff on Windows really struggled. If you're very careful with the tooling you may get lucky, but I watched as things like Chef, Sensu, and Collectd all took significantly more effort on the Windows platforms.
- larrywright 10y agoMore recent versions of Windows Server have definitely improved, but this is still pretty accurate. When given a set of tasks to do for Windows and Linux, the latter is always easier. If it takes x amount of time to automate something on Linux, it's 5x on Windows. Every time. Some of this is due to MS themselves, some of it is due to the software vendors, but it's a very real thing.
- severino 10y agoI doubt any of those 100.000.000.000 commercial products that need MSSQL would run on Linux either. In fact, even SQL Server Management Studio is a Windows-only application.
- pmelendez 10y agoThey don't have to. Let's say an enterprise wants to go start moving its backend to the cloud. Now there is a very significant price difference between windows instances and Linux instances. The client commercial product can still run on Windows and the database in Linux
- tracker1 10y agoFor that matter, it's been surprisingly easy to get ASP.Net apps to run with mono or .net core in some cases. ymmv of course, and the performance will vary, but it's an option.
- dogma1138 10y agoActually a lot of them do it's not hard to find some ticketing system or a call center management system that is written in JAVA or PHP and only works with mssql or oracle dbms. The app stack is usually more platform agnostic than you think. Even if it's asp.net you most likely going to be able to run it or easily port it to .net core. Basically having cross platform .net is pointless without having cross platform everything else especially MSSQL.
- tracker1 10y agoI was surprised how easy it was to get a couple asp.net apps running under docker dotnet-onbuild base containers... I think having SQL Server under linux/docker is a really nice option. Just being able to use it with ci/cd environments in linux is a pretty big thing. I've moved more away from the MS environments the past few years now, but have missed some of the things that MSSQL makes very easy, and by comparison PostgreSQL makes relatively hard. Of course you're paying for it. Having the option to run under Linux is really nice though imho.
- rbanffy 10y ago> having to rewrite your entire DB access and query code. Anyone who has to do that is doing (or did, in the past) something seriously wrong. For me, the biggest reason not to change database after you accumulate a couple dozen terabytes of data is the inconvenience of dumping and restoring it and the downtime it'll cause.
- paulmd 10y agoIt all depends on how much of your "program" lives in the database, in terms of things like triggers, stored functions, etc. That's the argument against those things - it makes it difficult to switch your database. But there are also some compelling performance arguments in some cases, so in a well-designed system those parts of the code that live in the DB also tend to be important ones.
- rbanffy 10y agoThis is pretty much the kind of "wrong" I meant. ;-) In this case, it's still wrong, but faster than doing it right.
- flukus 10y ago> That's the argument against those things - it makes it difficult to switch your database. But there are also some compelling performance arguments in some cases, so in a well-designed system those parts of the code that live in the DB also tend to be important ones. But if they only exist for the critical parts then porting is a lot easier.
- irrational 10y agoWhy? I am in the process of moving from Oracle to Postgres right now (we no longer want to pay the Oracle tax). It has taken me months of work, but I am almost done. I've been very very impressed with Postgres so far and am amazed by how much better its documentation is than Oracle's. This required rewriting thousands of queries (I now how a pretty good list of differences between oracle and postgres!), but it feels good to almost be done. But now I read that all the work I have been doing is seriously wrong. Why?
- closeparen 10y ago>it has built in solutions for HIPPA and PCI What? HIPPA, point by point [0]. - Do periodic risk assessments and be able to produce the reports if demanded. - Have a designated HIPAA compliance officer. - Have a security policy, train employees on it, and ensure it has sufficient teeth to terminate violators. - Follow the principle of least privilege when granting access to PHI. - Limit physical access to facilities. - No shared accounts, and lock workstations when idle. - Encrypt data at rest and in transit. - Log data access. - Protect data against corruption. I suppose an RDBMS can help protect data integrity through foreign key constraints and other validation tactics, but the rest of this can't really be performed at database engine layer (unless your users are logging in to MSSQL directly?) so much as the EMR application and the physical, config management (full disk encryption + screensaver password), and bureaucratic environment it's deployed in. [0] https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/ https://www.hhs.gov/hipaa/for-professionals/security/laws-re...
- simcop2387 10y ago> - Encrypt data at rest and in transit. > - Log data access. > - Protect data against corruption. It's these three that I imagine MSSQL can help with. I believe it's got a built in storage encryption setup for tables/databases and can definitely be setup to log access to the database and queries run against HIPAA data.
- dogma1138 10y agoIt's got cell level TDE if you want which also makes it transparent to the application which makes it pretty easy to implement as you don't need to handle the encryption within your app. All the key management, split knowledge, key rotation and most importantly access management and a full audit trail are also a "few clicks" away. Having a turn key solution for one of the most annoying things to implement in a correct manner should not be under-estimated. Anyone who done any compliance work knows just how many weirdly stitched solutions you can have. Something along the lines of "we manage split knowledge to our keys by splitting the key and keepass file into 2 files and storing them on USB keys in separate vaults".... Now technically this can pass a compliance check but this is a pretty darn silly situation simply because there isn't any better solution that works out of the box, this also quite often means that anytime you restart your DB you have an entire process of getting the keys, decrypting the tables copying their content into temporary views, re-encrypting the files and remove the keys from the server.. For MSSQL it wasn't that long ago that you have to do it "by hand" also, usually have a stored procedure that would handle the encryption and have a key which is then encrypted by several KEK's whilst it did afford some split knowledge it wasn't a true m of n which also meant that if you had more than 2 DBA's you had to make sure that the DBA's are know all of the KEK's and not be in a situation where all 3 DBA's that are not off during that week know the exact same password for the KEK...
- partycoder 10y agoMany superlatives here. Better, easier, faster... than what? Against which other product did you compare against? There are many database systems supporting Linux. IBM DB2, Oracle Database, to mention a few.
- dx034 10y agoThe parent comment asked for a comparison to postgres. So that's the benchmark here. Oracle will of course be different but is also paid.