Re: Oracle out the door

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:

1. Regular rebuilding of indexes and reclaiming space.
2. Temp "result" tables are the norm for programming.
3. Escalating Blocking Lock City!
4. Cursors are evil here.
5. Troubleshooting is easy: Reboot
6. A hier-WHO-cical query???
7. Indexes mixed in with table pages ("Charlie Foxtrot" in military jargon)
8. Corrupted pages ("blocks" to the Ora DBA).
9. Everything should be in "dbo", right?
10. Welcome to 1990!

Upper management probably won't care about any of this until it's too late. At least shoot for EnterpriseDB (paid PostgreSQL) -- they're specifically targeting installed Oracle bases.

GL!

Rich

> The new CIO at my current employer brings a lot of preternatural hate
> for Oracle licensing as well. So much so that the upcoming data
> warehouse project for our Oracle OLTP instance is slated to be on SQL
> Server.
>
> On Tue, Apr 29, 2008 at 1:39 PM, John Thompson <jhthomp_at_gmail.com> wrote:
>> Company I work for just announced that we're going to convert all but 2 of
>> our 89 Oracle databases to either SQL Server, MYSQL, or PostgreSQL. This
>> is due to the high licensing cost. I'm bummed.
>
> --
> Don Seiler

--
http://www.freelists.org/webpage/oracle-l