SQL vs Oracle

[Donna]

I am starting to develop an application in SQL and VB6 and MTS. My company
is leaning towards Oracle. How can I convince management to use SQL? I
don't know anything about Oracle, and I need information..... )

[Eric Ford]

My company writes applications that must be able to support any customer configurations
using Access, SQL Server, and, Oracle (though not all at the same time).
The best approach to dealing with this is to make maximum use of stored
procedures (stored queries in Access). That way your VB code need not care
what backend is selected. Coding on the backend just needs to conform to
the same stored procedure interfaces (i.e., procedure name and parameter
list).

Eric

"Donna" <djsund@hotmail.com> wrote:
>
>I am starting to develop an application in SQL and VB6 and MTS. My company
>is leaning towards Oracle. How can I convince management to use SQL? I
>don't know anything about Oracle, and I need information..... )

[Bill Vaughn]

Often the choice between SQL Server and Oracle has more to do with office
politics, and with what the developers, managers, owners and their cousins
already know and are familar with. Both Oracle and SQL Server have loyal
followings. I'm obviously biased toward SQL Server and given that, also consider
that the number of unresolved questions, problems and issues regarding Oracle
and VB seem to be greater than those regarding SS. Visual Studio was designed
to work against both systems (and others), but certaily favors SS. There
are more features, more integration and better doc, books, training etc with
SS. And if you are considering performance, SS has shown to be much, much
faster and cheaper to implement that Oracle. We didn't used to be able to
say that with a straight face--now we can with Windows 2000 and SQL Server
2000.

As far as writing a single application that can take advantage of the features
of both at the same time--I've never seen one. I have seen apps that try,
but end up compromising performance, features and reliability to try to make
it work. I for one, would avoid these "generic" systems.
"Eric Ford" <Eric_S_Ford@hotmail.com> wrote:
>
>My company writes applications that must be able to support any customer
configurations
>using Access, SQL Server, and, Oracle (though not all at the same time).
> The best approach to dealing with this is to make maximum use of stored
>procedures (stored queries in Access). That way your VB code need not care
>what backend is selected. Coding on the backend just needs to conform to
>the same stored procedure interfaces (i.e., procedure name and parameter
>list).
>
>Eric
>
>"Donna" <djsund@hotmail.com> wrote:
>>
>>I am starting to develop an application in SQL and VB6 and MTS. My company
>>is leaning towards Oracle. How can I convince management to use SQL?
I
>>don't know anything about Oracle, and I need information..... )
>