Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: Oracle 9i first impressions.
I'll say this for it though. It makes what is happening clearer. You are connecting to the database as a user with a set of highly elevated privileges. Connect internal always seemed like a way of saying 'you are now entering the weird, weird world of incomplete recovery, beware monsters await'
Admittedly this isn't an entirely reasonable reason to ditch the syntax ;-)but it makes me feel better.
-- Niall Litchfield Oracle DBA Audit Commission UK Legal disclaimer required by my employer **************************************************************************** *********************** This email contains information intended for the addressee only. It may be confidential and may be the subject of legal and/or professional privilege. Any dissemination, distribution, copyright or use of this communication without prior permission of the addressee is strictly prohibited. **************************************************************************** *********************** "Daniel A. Morgan" <Daniel.Morgan_at_attws.com> wrote in message news:3B4DECA8.AF4195C5_at_attws.com...Received on Sat Jul 21 2001 - 16:35:16 CDT
> Xuequn Xu wrote:
>
> > So, "connect / as sysdba" has been around in 7.x, 8.x, 9.x ...
> > The focal question is, what's the difference (with "connect internal")?
> > They are both using OS authentication, and the only difference
> > seems to be the letters to type after "connect ...". So what's the big
deal
> > of making "connect internal" un-supported?
>
> Not that I care ... as I just go with the flow ... but it does strike me
as being
> change for the sake of change. If there is no significant difference why
not
> leave well enough alone? I can certainly appreciate dropping server
manager but
> the this change appears to be gratuitious.
>
> Daniel A. Morgan
>
![]() |
![]() |