Do you know where I can find help in translating Oracle SQL queries to MSSQL queries?
The whole idea behind a SQL "standard" is that vendors will follow it and SQL will be portable. If SQL really is that abstraction layer between us and the guts of the DBMS, it shouldn't matter what's on the back end. As you already know, vendor implementation of SQL can vary quite a bit. Even so, moving from Oracle's SQL to SQL Server's SQL shouldn't be too hard of a jump. Major differences include that fact that SQL Server supports different data types than Oracle. Also, data type conversion functions are very different, unless you are using the standard SQL CAST syntax. SQL Server has Identity columns where Oracle has Sequences. SQL Server has supported SQL-92 style joins for a while; Oracle's 9i now supports them. If you've used the (+) outer join syntax of Oracle, you will need to rewrite them. About a year ago, I found a good resource for SQL Server for those with an Oracle background. It is written by Microsoft, so you can expect it to be a little slanted. Also, it's a bit outdated, as Oracle9i wasn't out when it was published. It's published at http://www.microsoft.com/sql/techinfo/deployment/2000/MigrateOracle.asp.
For More Information
- What do you think about this answer? E-mail the edtiors at editor@searchDatabase.com with your feedback.
- The Best SQL Web Links: tips, tutorials, scripts, and more.
- Have an SQL tip to offer your fellow DBAs and developers? The best tips submitted will receive a cool prize. Submit your tip today!
- Ask your technical SQL questions -- or help out your peers by answering them -- in our live discussion forums.
- Ask the Experts yourself: Our SQL, database design, Oracle, SQL Server, DB2, metadata, object-oriented and data warehousing gurus are waiting to answer your toughest questions.
Dig Deeper on Oracle and SQL
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.