Re: Oracle6->Oracle7 Conversion
Date: 20 Mar 93 19:41:31 CST
Message-ID: <1993Mar20.194131.1350_at_hermes.dlogics.com>
In article <1993Mar17.201234.10997_at_netcom.com>,
sjs_at_netcom.com (Stephen Schow) writes:
> ...In other words, we have a number of applications in place under V6 and we
> want to upgrade to V7. Step 1 would be to just get the existing apps working
> properly under V6 with existing security, etc... Step 2 MIGHT be to upgrade
> the applications to include new V7 functionality such as store procedures...
>
The charm ;-) of v7 is that you don't actually have to do anything to your
v6 apps to keep them running. even the much-feared char-to-varchar2 conversion
is automatic if you export under v6 and import to v7.
My take on the v6-to-v7 thing is: if, after the upgrade, the app works, do not change it for v7's sake; new apps developped under v7 can take advantage of all the new stuff.
In many cases, the rdbms is ahead of the tools; you cannot always use the new v7 features from sqlforms, oragraphics, reportwriter, &ca. So it may be too early for any practical effect on your apps!
The only "dba" thing i noticed was the need to greatly expand the SGA size; doubling your v6 value is not all that bad a first-guess.
-- Dave Mausner, Senior Consultant / Datalogics Inc / Chicago IL / 312-266-4450 dlm_at_dlogics.com Motto: Just show me the codeReceived on Sun Mar 21 1993 - 02:41:31 CET