I am not sure, as I am not as well versed on the admin side of Oracle. As
long as the SYSDBA user can be named or aliased (for a connection string), I
see no reason why not. I would be wary about where you store this
connstring, however; encryption would be a must for this type of secret.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
**********************************************************************
Think Outside the Box!
**********************************************************************
"Eidolon" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> We currently use the Microsoft Native .NET Provider for Oracle to do our
> connections with...
> For one app we really need to be able to connect to the db as a SYSDBA
user.
>
> Does anyone know how this can be done using the MS.NET Oracle provider??
>
> Thanks in advance,
>
>
|