Re: Oracle linked server : won't run if driver AllowInProc is off

From: H.Rosental (HRosental_at_discussions.microsoft.com)
Date: 01/07/05 

Date: Fri, 7 Jan 2005 07:55:01 -0800

I think you hit the problem. I was having the same issues until I decided to
test it under the local system account instead of the domain account my SQL
Server was originally set.

Under the local system account, I had no problems setting a linked Oracle
server, in proc or out of proc, but when SQL Server is running under the
domain account, the connection doesn't work.

I've try to place the domain account in my local adminstrator group, but
that doesn't work either.

I've left my SQL Server running under my local system account for now, if
someone knows a fix for this issue, please post it.

H.Rosental
"/dev/null" wrote:

> I just tested using an ODBC data source using the Microsoft ole db for Oracle
> driver and it's the same issue. Is it because we set up SQL server to run
> under a specific user account (not localsystem or whatever the default is) ?
>
> the linked server was set up to use an odbc source, a source which used the
> same driver as before...
>
> and the fun won't stop!
>
> "/dev/null" wrote:
>
> > We don't want to run the driver in process for the reason you thought: sql
> > server crashes = we better run damn fast for our lives.
> >
> > It's not that i didn't try the driver provided by oracle but i never got it
> > to work. It seemed even more trouble than the microsoft driver. Even then i
> > suspect we'd have to be running it in-process.
> >
> > "David Browne" wrote:
> >
> > > "Bhanu" <SQLDBA1999@yahoo.com> wrote in message
> > > news:%23sqDSm3tEHA.2128@TK2MSFTNGP11.phx.gbl...
> > > > Why don't you use oracle driver instead? You can install ORACLE client on
> > > > the SQL box and you should be able to get it working with no issues.
> > > >
> > >
> > > The Oracle Client is required for MSDAORA as well, so it is already
> > > installed on the box. I assume that the OP is uncomfortable running the
> > > Oralce OleDb drivers and the Oracle Client inside the SqlServer address
> > > space for fear it could crash Sql Server.
> > >
> > > And quite honestly, I would not allow ad-hoc queries to an Oracle linked
> > > server with the Oracle Client in-process in a production Sql Server. With
> > > canned queries and testing, ok, but it's still a concern.
> > >
> > > David
> > >
> > >
> > >

Relevant Pages

  • Re: Scheduling DTS job
    ... Local System account has unrestricted access to the local box and cannot see ... The day schedule took just as long as overnight right? ... Would this take as long "SQL Server to SQL Server"? ... package involved data transferred from sybase to ...
    (microsoft.public.sqlserver.dts)
  • Full text HELP!!!
    ... 1- full text service is running under local system account ... 2- sql server is running under a domain account ... admins need to be in the logins.. ...
    (microsoft.public.sqlserver.fulltext)
  • Re: https and Local System account
    ... I'm not sure that this is an IIS issue - IIS would respond to your request. ... You probably need to take this up in an SQL Server forum if you are attempting to invoke something from an SQL Server trigger ... I would like to make a https call under Local System account ... under Local System account and http call there is no problem too. ...
    (microsoft.public.inetserver.iis.security)
  • Re: Scheduling DTS job
    ... How do i see if there is any difference in the driver ... >driver setup ... >> The SQL server agent is running as Local System Account. ...
    (microsoft.public.sqlserver.dts)
  • Re: Scheduling DTS job
    ... If you try to transfer the same rowsfrom SQL Server to SQL Server ... > How do i see if there is any difference in the driver ... >>> The SQL server agent is running as Local System Account. ... >>> Nothing has been changed in sybase box. ...
    (microsoft.public.sqlserver.dts)