March 19, 2008 at 11:10 am
I've recently (about 5 minutes ago) accepted a job as an Oracle DBA, Don't suppose anyone knows of any Oracley type websites that are as good as sqlservercentral.com? I've come across a few but none seem as good as this place.
I'm only doing it for a learning experience and to bump up my all round DBA skills, not to mention having a good understanding of Oracle can only help nowadays.
March 25, 2008 at 8:38 am
March 25, 2008 at 8:47 am
March 26, 2008 at 4:38 pm
How about reading this very thread from this very forum?
Gints Plivna
Gints Plivna
http://www.gplivna.eu
March 27, 2008 at 7:20 am
gints.plivna (3/26/2008)
Gints Plivna
http://www.gplivna.eu[/quote%5D
Nah.... can't be bothered.;)
Seriously though thanks.
March 28, 2008 at 2:11 pm
For solutions to Oracle 'How to' questions: asktom.oracle.com
Tom Kyte is the man!
April 9, 2008 at 11:52 am
oracle tech network is good too ... (OTN)
April 9, 2008 at 2:20 pm
You received a lot of sites to visit, but the best of all the oracle site.
is not as bad as it looks, I have been an oracle DB/SQL DBA for a long time. I have a lot of fun working with both.
"We never plan to Fail, We just fail to plan":)
September 16, 2008 at 8:46 am
http://www.dbasupport.com/forums/forumdisplay.php?f=20
_____________________________________
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.September 16, 2008 at 9:32 pm
As other DBAs have mentioned earlier in this post orafaq is a good one, Oracle itself has metalink with the new dashboard functionality (which is rather nice in a gui type of way)... You'll find Oracle does what SQL does but as always in a slightly different way. I've work with Oracle for 15 years and SQL for 5 years and I find each year they become more alike. The terminology may stump you for a while as the same thing is called by two different terms depending on which product you are using at the time.
Adonia
September 17, 2008 at 3:14 am
I'm in agreement with Adonia but I would characterize Metalink as a Knowledge Base rather than a simple user forum.
_____________________________________
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.September 18, 2008 at 12:15 am
You'll find all the Oracle documentation at http://www.oracle.com/technology/documentation/database.html including some quick start guides.
September 18, 2008 at 8:52 am
Syntax will probably be the least of your concerns. However, I just completed a project where I had to convert many, many scripts from Oracle to Sql Server. Here are some notes I put together for us:
Oracle -> Sql Server script conversions
1. NUMBER -> INT
2. VARCHAR2 -> VARCHAR
3. DATE -> DATETIME
4. := -> =
5. sysdate -> getdate()
6. then -> begin
7. end if -> end
8. loop -> begin
9. || -> +
10. Select count(*) into v_variable -> Select @v_variable = count(*)
11. CREATE OR REPLACE PROCEDURE ->
IF EXISTS ( SELECT 1
FROM INFORMATION_SCHEMA.ROUTINES
WHERE routine_type = 'PROCEDURE'
AND routine_name = 'prc_example' )
DROP PROCEDURE prc_example
GO
Variables
12. All variable declarations must have a DECLARE statement
13. Variables can not be assigned a value in the DECLARE statement. They must be DECLAREd and then SET. This is not true for parameters of stored procedure: default values can be assigned.
14. All variables must be appended with set @
Stored Procedures
15. All calls to stored procedures must begin with an EXEC
16. When executing stored procedures in Sql Server, do not use parenthesis around the variable declarations (IE. EXEC my_proc @var1 var2 and not EXEC my_proc(@var1, var2)
17. Output variables in a stored procedure must be declared, not so for input variables. (IE. EXEC my_proc2 @var1, var2 OUTPUT)
18. Can not pass a concatenated string to a stored procedure. You must put the string into a variable and pass the variable to the stored procedure.
September 18, 2008 at 9:16 am
abba (9/18/2008)
Syntax will probably be the least of your concerns.
:w00t: I respectfully disagree 🙂
_____________________________________
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.September 18, 2008 at 2:31 pm
PaulB (9/18/2008)
abba (9/18/2008)
Syntax will probably be the least of your concerns.:w00t: I respectfully disagree 🙂
I'll agree with that disagreement... syntax changes will be a doozy. Wait until you try to return a result set to an app from a stored procedure... lookup "Reference Cursor" and "Packages" for a leg up on that.
What ever possesed you to join the darkside?
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 15 posts - 1 through 15 (of 24 total)
You must be logged in to reply to this topic. Login to reply