|
They should have declared when they were 100 ahead and put them in again. Finish the game of in one day. 
|
|
|
|
|
Going from SQL Server to Oracle.
Say goodbye to good tooling.
Say goodbye to civilized (T-)SQL (I think the PL in PL/SQL means Oracle outsourced the language to some cheap Polish labor... (no offence to Polish people)).
Say hello to steep learning curve.
All in all I just miss SQL Server.
Any "surviving Oracle for SQL Server devs" tips or guides? 
|
|
|
|
|
You might ask the oracle... 
|
|
|
|
|
They should've called it Miracle instead.
It's a Miracle anyone can get work done with this crap 
I'm sure it'll get better as I figure this out...
|
|
|
|
|
Sander Rossel wrote: Any "surviving Oracle for SQL Server devs" tips or guides?
Tips and guides[^] 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Been using oracle at work since the last 7 months, and I feel satisfied.
No idea about
Sander Rossel wrote: "surviving Oracle for SQL Server devs"
I developed the database of my final year project in SQL server, it was pretty good. But haven't used SQL server on professional level yet.
But yeah it's very difficult to search for the solution of oracle problems on internet, you rarely find anything except the hell lengthy and descriptive oracle documentation, which you just damn hate to read
|
|
|
|
|
I moved from SQL Server to Oracle for around 4 years and am back on SQL Server now.
There are differences although the differences are not that big nowadays as SQL Server has come closer to Oracle.
The hardest part for me was discovering that many Oracle developers tend to have a preference for non-ANSI joins.
Get yourself a book on PL/SQL clicketty[^] and you should be fine.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
Sander Rossel wrote: I think the PL in PL/SQL means Oracle outsourced the language to some cheap Polish labor... (no offence to Polish people)
aaaah! so thats what PL stands for!
#region(start signature)
Life's like a nose, you've got to get out of it whats in it!
#endregion
|
|
|
|
|
I actually prefer Oracle to SQL Server, hands down. I just wish Oracle was able to integrate with Visual Studio at the same level SQL Server does.
Anyhow, PL SQL is awesome stuff when done correctly, and used correctly.
BTW, you can use Entity Framework with Oracle, you just need to install the Visual Studio tools for Oracle.
|
|
|
|
|
For years I used Oracle and SQL Server interchangeably, there are slight differences in certain things (like wildcard character), but otherwise, I really like Oracle.
I strongly recommend Toad[^] for a decent tool to work with Oracle.
Marc
|
|
|
|
|
+1 for Toad - invaluable !
PooperPig - Coming Soon
|
|
|
|
|
Yeah, I looked at Toad, but it's not cheap...
My company has their own in-house editor of which they're very proud, so there's no way they're going to buy some external editor.
I didn't like the in-house one though, so I downloaded the free Oracle SQL Developer[^] which is a step in the right direction 
|
|
|
|
|
Or, you may want to have a look at PL/SQL Developer by dutch AllRound Automation. I have been using it for years and I am very pleased with it. Doesn't have as many features as Toad, but then it is generally faster to use.
http://allroundautomations.com/[^]
|
|
|
|
|
|
I'm not doing anything Unix and I try to avoid command lines as much as possible on any OS 
|
|
|
|
|
Congratulations!
You are talking job security well into your 80's!![Rose | [Rose]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/rose.gif)
|
|
|
|
|
Vivic wrote: job security well into your 80's
Might as well do some COBOL then 
|
|
|
|
|
But then you will not be stark raving mad!
|
|
|
|
|
Sorry, I have no advice but have read some of your articles.  I have no doubt you'll pick it up quickly! Great opportunity to broaden your skillset. Have fun! 
"Go forth into the source" - Neal Morse
|
|
|
|
|
|
It's strange you worry about T-SQL/PL-SQL at all! It's atavism from 70-th. Nowadays application server does it much better, so on database side you leave just tables and SQL requests - they are "almost compatible" across all databases.
|
|
|
|
|
Yeah, but how to make the tables, procedures, etc. It's quite a difference.
Oracle has procedures which can't return a result, only output parameters, while in SQL Server a procedure is like Oracle's procedure and function in one and SQL Servers function is quite different from the Oracle function... etc. etc.
And I just found out Oracle doesn't know the bit/boolean type... 
And while an application server might do it better a database will generally do it faster
|
|
|
|
|
and once you have learned Oracle PL/SQL it will be easy for you to code Postgres plpgsql - almost identical .
|
|
|
|
|
Ask for a pay raise/rise. If your organization/organisation can afford Oracle, they are obviously swimming in cash. My organization could save money by moving in the other direction to PostgreSQL, but fat chance of that.
|
|
|
|
|
As a supplier of Oracle it costs us nothing.
It's our customers who can afford it
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
