Re: Oracle out the door

Some counterpoint to Niall's comments:  :)

On Tue, Apr 29, 2008 at 12:38 PM, Rich Jesse <
rjoralist@xxxxxxxxxxxxxxxxxxxxx> wrote:

> Having added SQL Server 2K/2K5 to my resume in the past year I can offer a
> SQL Server hit list for the seasoned Oracle DBA:
>
>
> 9)  Temp "result" tables are the norm for programming.
>

Due to SQL Server being unable to do consistent reads.
Just had this conversation with a (very good) developer the other day.
He was quite surprised that no temp tables were required in Oracle
for the purpose of providing a consistent view of the data.


> 5)  A hier-WHO-cical query???


During a recent acquisition, much data was moved from SQL Server
to Oracle.  Much code was not required in Oracle that has been required
in SS to create a BOM (Bill Of Materials)

BTW, if you work with BOM's don't talk about it when traveling.

2)  Everything should be in "dbo", right?


We have some canned apps that will not work if not dbo.

-- 
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist

Other related posts: