SQL Server seems maybe too focused on usability. Oracle's query interpreter, for example, is extremely anal, you have to commit everything and Oracle is likely

SQL Server seems maybe too focused on usability. Oracle's query interpreter, for example, is extremely anal, you have to commit everything and Oracle is likely to reject your queries if they are slightly off, which helps catch errors. SQL Server follows more of a "Do What I Mean" approach, even going as far as to perform implicit type conversions for you, which is fine until it guesses wrong. Then, instead of rejecting your query, it screws up your data. And don't tell me I can configure it to behave differently, it should work correctly out-of-the-box.