The real pain comes when you try comparing the old vendor specific OUTER JOIN syntax for Oracle and SQL Server. I guarantee you'll love JOIN ... ON ... over comma joins.
Oracle:
SELECT *
FROM T1, T2
WHERE T1.PK1 = T2.FK1(+)
SQL Server: SELECT *
FROM T1, T2
WHERE T1.PK1 *= T2.FK1
Note that the outer indicator goes on the opposite side. Oh, and, of course, if you flip the order of the fields around, you've got to remember to flip the (+) operator. Which of these three are identical: SELECT *
FROM T1, T2
WHERE T1.PK1(+) = T2.FK1
SELECT *
FROM T1, T2
WHERE T2.FK1(+) = T1.PK1
SELECT *
FROM T1, T2
WHERE T2.FK1 = T1.PK1(+)
Now imagine you're joining 5 tables and want to reuse the JOIN syntax.Yeah. Fuck that. I'll take this any day:
SELECT *
FROM T1
LEFT JOIN T2
ON T1.PK1 = T2.FK1Even Oracle's own documentation[0] tells you to avoid the (+) syntax:
> Oracle recommends that you use the FROM clause OUTER JOIN syntax rather than the Oracle join operator. Outer join queries that use the Oracle join operator (+) are subject to [several restrictions], which do not apply to the FROM clause OUTER JOIN syntax[.]
The doc itself lists all the issues, which is about 10 of them. None of these are opinions, either. They're actually technical limitations with (+), though they may not be ones that you encounter. The only advantage I know of for the (+) syntax is some uncommon issues with materialized view optimizations.
[0]: https://docs.oracle.com/cd/B19306_01/server.102/b14200/queri...