July 22, 2011 at 9:45 am
Both platforms have issues, as well as pros.
I would tend to stick with what the skills of my staff were since the cost of the system can be low compared to the cost of people, and the cost of training them.
The patch issue is a little silly. *Nix gets patches every month as well. I watch the security list and see kernel patches flow through regularly, and there are regular patches coming out for lots of the software that is included in *nix systems.
In both cases, you don't necessarily need to apply those patches every month. Choose the ones that matter to you, and apply them.
The same thing for SQL patches. SQL releases CUs every other month, but they don't necessarily all need to be applied. Oracle releases patches less often, but that's good and bad. Issues can sit for a long time before they're fixed.
SQL Server and Oracle are largely on par with one another in most places, except for cost. Oracle has a substantial cost over SQL Server, which is good for the DBAs. They tend to make more.
It seems many companies these days are mixed places, running both platforms if they are of any size.
July 22, 2011 at 10:42 am
We use SQL Server as our database platform, but still have other RDMS in use because they came embedded in software packages.
I know we have Oracle, SYBASE, MySQL, Informix, and DB2 in use with particular products. Probably some others that I am not aware of.
I think the same is probably true in shops that use Oracle as their database platform. It's probably even more difficult to keep out SQL Server when you consider all the products with SQL Express or MSDE embedded in them.
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply