Oracle books for Sql server DBA
-
I need to learn more about oracle, is anyone aware of any books that is really helpful for an Sql server dba moving into the oracle world.
Thanks.
Bunmi
-
-
Any of the Oracle (10g or 11g) DBA Handbooks written by Kevin Loney and Bob Bryla are good.
Good websites to look at are:
http://www.oracle.com/technology/index.html
Also Oracle Metalink has a good knowledgebase.
Good Luck with the new job.:)
-
I've been there, I done that.
1 Brace for impact, keep your poker face no matter what you see.
2 All Oracle documentation is online and free... try http://www.oracle.com/pls/db102/portal.all_books
3 Subscribe a good forum like... http://www.dbasupport.com/forums/forumdisplay.php?f=1
Good luck and have a lot of fun
_____________________________________
Pablo (Paul) BerzukovAuthor 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. -
PaulB (8/2/2008)
I've been there, I done that.1 Brace for impact, keep your poker face no matter what you see.
2 All Oracle documentation is online and free... try http://www.oracle.com/pls/db102/portal.all_books
3 Subscribe a good forum like... http://www.dbasupport.com/forums/forumdisplay.php?f=1
Good luck and have a lot of fun
Took the words right out of my mouth... and keep in mind that Oracle can't return result sets from stored procedures... you have to populate what is known as a "Reference Cursor". Also, you can't do simple tests like...
SELECT SYSDATE
... Instead, it must be...
SELECT SYSDATE FROM DUAL
...DUAL is a table with one empty row in it. And get real used to having a semi-colon in the wrong place.
Set based triggers are out of the question, as well. They have "trigger variables", not trigger tables.If you use SQLPlus, don't forget to SET BLANK_LINES ON; or you'll get a wealth of errors that don't make sense. And, if you use TOAD as your edit tool, you'll find that not everything that runs fine in TOAD will run at all in SQLPlus because of things like SET BLANK_LINES ON;
Also, no "PRINT"... you either have to use "PROMPT" or the DBMS_OUTPUT function.
The date functions are drastically different, as well. And UPDATE has no FROM clause... you MUST use correlated subqueries, instead. Of course, the work around for that is to use the "new" MERGE statement... and don't forget that you have to COMMIT all inserts, updates, and deletes.
The differences between Oracle and SQL Server are proof possitive that SQL is NOT SQL everywhere... well, unless you want to limit yourself to only (supposedly but not true) "portable" ANSI SQL. That's kinda like having a scientific calculator and only using the 4 basic math functions.
The paradigm shift between Oracle and SQL Server, no matter which way you're going, is huge! You'll also find that most people that start in SQL Server hate Oracle, and vice versa.
--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.Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally) -
You'll also find that most people that start in SQL Server hate Oracle, and vice versa.
Thanks God I'm not "most people"
I just do whatever pay the bills _____________________________________
Pablo (Paul) BerzukovAuthor 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. -
As we have already discussed many things in thread mentioned above
just a few notesJeff Moden (8/2/2008)
Of course, the work around for that is to use the "new" MERGE statement...New only for not yet existant SQL Server 2008, not for Oracle
The differences between Oracle and SQL Server are proof possitive that SQL is NOT SQL everywhere...
Just like cars - Ferrari isn't Bentley and Opel isn't Mazda and people are not surprised about that
Gints Plivna
Gints Plivna
http://www.gplivna.eu -
That's why I put "new" in parentheses... haven't need MERGE in SQL Server
--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.Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)
Viewing 8 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply