Eric M Russell (9/20/2012)

---

Lynn Pettis (9/19/2012)

---

Eric M Russell (9/19/2012)

---

Lynn Pettis (9/19/2012)

---

tutblog1 (9/19/2012)

---

Want to learn SQL?

Goto

easysqlguide.blogspot.in

Easily learn SQL with the help of images.

Two year old thread, and no, I don't want to learn SQL from your blog. I already know SQL.

So, after two years, how what's your overall impression of Oracle versus SQL Server?

Only worked with Oracle for a year. I am GLAD to be back working with SQL Server. There are a few things that I liked about Oracle, but I really think SQL Server does more things in a better way. Could be 15+ years of using SQL Server talking there.

In Oracle, an empty string is null ('' IS NULL), and consequently an empty string is not equal to itself. This evaluates as False: ('' = ''). For those of us who speak Oracle SQL as a second language, that can result in some bugs that are very subtle and hard to track down. I can live with proprietary functions and even minor syntax differences between SQL implementations. However, I just can't get past the fact that a major database vendor would have the default definition of NULL not conform to ANSI standard. As far as I know, there is no equivalent to a "SET ANSI_NULL ON" setting etiher.

Another observation is that (this is just my opinion), because Oracle is such a configurable RDMS platform and also contains so much legacy baggage, Oracle developers are not as well rounded on their own platform as SQL Server developers are. They learn how to implement something one way, but there may be 3 or 4 ways of doing it under Oracle. There are also tons of configuration settings, many of which have security implications, that the average Oracle DBA is not aware of. In contrast, SQL Server has a much smaller area of exposure, and for that reason is generally considered more secure out of the box.

In Oracle, an empty string is null ('' IS NULL), and consequently an empty string is not equal to itself.