SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Making the leap Sql Sever from Oracle


Making the leap Sql Sever from Oracle

Author
Message
David O
David O
SSC Veteran
SSC Veteran (298 reputation)SSC Veteran (298 reputation)SSC Veteran (298 reputation)SSC Veteran (298 reputation)SSC Veteran (298 reputation)SSC Veteran (298 reputation)SSC Veteran (298 reputation)SSC Veteran (298 reputation)

Group: General Forum Members
Points: 298 Visits: 928
Hired a solid tech with a great Oracle development background but need him to do Sql Server development now. He is trying and making progress but I'd like to shorten the learning curve.


Does anyone know of any training like this except for development:

http://msdn.microsoft.com/en-us/dd548020.aspx

Thanks,

David
Jeff Moden
Jeff Moden
SSC Guru
SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)

Group: General Forum Members
Points: 90708 Visits: 41150
Since I've worked on both, I can give you some very good tips...

Step 1. Relax... SQL Server doesn't require things like Reference Cursors to return a result set. A simple SELECT will do it.

Step 2A. Forget everything you know about Cursors and While Loops. 99.9% of everything that can be done, can be done without either and will run MUCH faster in the process.

Step 2B. Make a mental paradigm shift (like my signature line says below)... stop thinking about what you want to do to a row and start thinking about what you want to do to a column.

Step 3. Break out Books OnLine (the help system in SQL Server). Read about every function and read about the double FROM clauses in UPDATE... they will save your bacon. Forget about using correlated subqueries in UPDATE and learn that UPDATE and SELECT can use the same kinds of joins.

--Jeff Moden

RBAR is pronounced ree-bar and is a Modenism for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
If you think its expensive to hire a professional to do the job, wait until you hire an amateur. -- Red Adair

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
PaulB-TheOneAndOnly
PaulB-TheOneAndOnly
SSCertifiable
SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)

Group: General Forum Members
Points: 5631 Visits: 4639
Good tips Jeff.

Also - if working on a data warehouse environment forget about: bitmap indexes, materialized views, star-transformation and query rewrite. SQL Server offers a much simpler yet solid platform.

By the way, also forget about the differences in between PL/SQL and SQL*Plus - the beauty of SQL Server is that relies on a single, powerfull T-SQL language.

_____________________________________
Pablo (Paul) Berzukov

Author of Understanding Database Administration available at Amazon and other bookstores.

Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Jeff Moden
Jeff Moden
SSC Guru
SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)

Group: General Forum Members
Points: 90708 Visits: 41150
PaulB-TheOneAndOnly (6/11/2010)forget about the differences in between PL/SQL and SQL*Plus - the beauty of SQL Server is that relies on a single, powerfull T-SQL language.


Excellent point, Paul. I never understood why Oracle chose to separate "SQL" from "PL/SQL".

--Jeff Moden

RBAR is pronounced ree-bar and is a Modenism for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
If you think its expensive to hire a professional to do the job, wait until you hire an amateur. -- Red Adair

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
PaulB-TheOneAndOnly
PaulB-TheOneAndOnly
SSCertifiable
SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)

Group: General Forum Members
Points: 5631 Visits: 4639
Jeff Moden (6/11/2010)Excellent point, Paul. I never understood why Oracle chose to separate "SQL" from "PL/SQL".


That's a very good question which puzzled me for a long time.

Even when I do not have a definitive answer to it I know SQL was introduced around 1979 - most probably version 4 - when PL/SQL is a "modern" days innovation from 1992 - Oracle version 7.

Since PL/SQL follows the general structure and syntax of Ada while SQL is nothing but the Oracle implementation of the more structurally simple IBM's SQL my guess is that integration of the two languages was beyond the scope of the project. I remember Oracle documentation from those days introducing PL/SQL as a structured extension of SQL.

_____________________________________
Pablo (Paul) Berzukov

Author of Understanding Database Administration available at Amazon and other bookstores.

Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search