Job runs for a long time in SQL Server Agent 2005

I have an exe in C# in .Net 1.1. This accesses an Oracle database and an SQL Server 2000 database. It is scheduled in SQL Server Agent. It runs for normally 30 seconds and stops

Recently we migrated the database to SQL Server 2005. We created this job manually in SQL Server Agent. Even after running for 3 minutes it never stops (abnormal)

However this exe runs normally in the Windows 2003 scheduler and the command prompt.

Am stumped for an answer.

Any help

Thanks and regards

jarathna

Do have relevant oracle client drivers installed on this SQL 2005 instance?

Ibelieve this is something related to the Operating system related process, if this is scheduled via SQLagent job then ensure SQLserver serivces do have relevant privileges on that C# & Oracle based components share.

JDBC with mulitple databases

Dear all,

Our application needs a bit of database redundancy.

Our application only accesses database for reading purposes.

We want to have two databases in separate machines. Incase one database
server dies the application should automatically extract data from the
other server.

Is there any JDBC driver available so that it can detect failure in the
main database server and then tries to extract data from the standby
database server?

Kind regards

--
Posted via http://dbforums.com
gbhatti wrote:

> Dear all,
> Our application needs a bit of database redundancy.
> Our application only accesses database for reading purposes.
> We want to have two databases in separate machines. Incase one database
> server dies the application should automatically extract data from the
> other server.
> Is there any JDBC driver available so that it can detect failure in the
> main database server and then tries to extract data from the standby
> database server?
> Kind regards

Not for SQLServer, but oracle has something like that if you have
oracle clustered DBMSes. However, it's not hard to write code
that will react to connectivity failure with one DBMS by connecting
to an alternate...

Joe Weinstein at BEA

> --
> Posted via http://dbforums.com|||"gbhatti" <member43992@.dbforums.com> wrote in message
news:3477901.1066098913@.dbforums.com...
> Dear all,
>
> Our application needs a bit of database redundancy.
>
> Our application only accesses database for reading purposes.
>
> We want to have two databases in separate machines. Incase one database
> server dies the application should automatically extract data from the
> other server.
>
> Is there any JDBC driver available so that it can detect failure in the
> main database server and then tries to extract data from the standby
> database server?

Not that I'm aware of. Typically this is done with SQL Enterprise in a
clustered format.

It is possible to encode it at the client level though also. But I'm not
aware of any JDBC driver that does it.

>
> Kind regards
>
> --
> Posted via http://dbforums.com