Re: I can attach in SQL Server, but can I in Oracle?

From: Ron Fluegge <rmflugge_at_swbell.net>
Date: Fri, 08 Aug 2003 22:08:58 GMT
Message-ID: <_bVYa.90$Rg2.34_at_newssvr23.news.prodigy.com>


Daniel,

First let me thank you for the civil response.

My app has been in testing for 9 months and does NOT corrupt either the SQL or Oracle tables.

If you are familiar with the .NET framework, I am using the Oracle managed providers that are provided by Oracle and are a part of the framework.

The single datalayer does NOT use OleDB or ODBC to interface with the DBs, but I-interfaces to connect to either Oracle or SQL Server.

Despite what you said, mine is working and to-date has not corrupted the Oracle tables.

I would suggest that you look closely at VS.NET 2003 and also at http://otn.oracle.com/tech/windows/odpnet/content.html

Again, thanks for the advice.

Ron

"Daniel Morgan" <damorgan_at_exxesolutions.com> wrote in message news:3F341778.55B119A9_at_exxesolutions.com...
> Ron Fluegge wrote:
>
> > First, I find your reply absurd ... especially in a newsgroup.
> >
> > I admitted up front that I was a "novice" at Oracle.
> >
> > However, if you were a "developer" you would know that it is also absurd
to
> > create two different versions of an application to support two or more
data
> > sources. That's the whole purpose behind a "data layer" in a
multi-tiered
> > application ... my datalayer IS WORKING with all of the 5 data sources
> > listed below. So I do apparently know more than you do about
application
> > development. (now stepping off of soap box).
> >
> > I would hope that the rest of the participants in this newsgroup would
be
> > willing to offer some "useful" advice.
> >
> > Ron
> >
> > "Sybrand Bakker" <gooiditweg_at_nospam.demon.nl> wrote in message
> > news:lop7jv0nqknstg8t08gi70j2siccug7f17_at_4ax.com...
> > > On Fri, 08 Aug 2003 18:00:28 GMT, "Ron Fluegge" <rmflugge_at_swbell.net>
> > > wrote:
> > >
> > > >First, let me apologize for the probably "simple and basic" question,
but
> > I
> > > >have searched both Google and Deja without success.
> > :
> > :
> > > >Please understand that I may not be using the correct terminology for
the
> > > >Oracle databases and tables -- I apologize.
> > > >
> > > >Any assistance would be greatly appreciated.
> > > >
> > > >Thanks.
> > > >
> > > >Ron Fluegge
> > > >
> > >
> > >
> > > You need to do the following things
> > > 0.a find the financial resources to learn Oracle
> > > 0.b alternatively hire a consultant
> > > 0.c redevelop the sqlserver app for Oracle. It is not going to work
> > > without change ever
> > > 0.d regret you decided Oracle is Sqlserver sold by a different vendor
> > > 0.e add several months to the release date
> > > 0.f forget all of the points outlined above: they are crap and show
> > > you don't know anything about Oracle
> > >
> > >
> > > Sybrand Bakker, Senior Oracle DBA
> > >
> > > To reply remove -verwijderdit from my e-mail address
>
> Seemingly absurd or not ... Sybrand's points are valid. Oracle is not SQL
Server
> sold by another company and if you are using the same code on both
databases you
> will at best have something that won't scale and at worst will corrupt
data.
>
> How to tell whether Sybrand is correct? How have you handled the
multiversioning
> concurrency model in Oracle?
>
> If you don't know what I am referring to ... reread Sybrand's post.
>
> Your desire to have a single code base is commendable but do understand
that you
> are hardly the first person to think it could be done. Unfortunately I
have been
> employed numerous times by "name" software firms to help them take apps
written
> for SQL Server and make them work with Oracle. The result is always a
rewrite:
> In part or in total.
>
> --
> Daniel Morgan
> http://www.outreach.washington.edu/extinfo/certprog/oad/oad_crs.asp
> damorgan_at_x.washington.edu
> (replace 'x' with a 'u' to reply)
>
>
Received on Sat Aug 09 2003 - 00:08:58 CEST

Original text of this message