We are currently evaluating the
Automation-Suite and created a
stored procedure that takes about
7 minues to be executed. When
we schedule it as a Job it stops
after 2-3 Seconds...

The same procedure called with the
same User from QueryAnalyser works
fine.

We used the Profiler as well to
see potential problems, but all
looks normal...

Any ideas?

Does this SP return any result sets or prints any diagnostic messages after 2-3 seconds of run?
Do you run it using ODBC interface or native driver interface?

: We are currently evaluating the
: Automation-Suite and created a
: stored procedure that takes about
: 7 minues to be executed. When
: we schedule it as a Job it stops
: after 2-3 Seconds...

: The same procedure called with the
: same User from QueryAnalyser works
: fine.

: We used the Profiler as well to
: see potential problems, but all
: looks normal...

: Any ideas?

: Does this SP return any result sets or prints any diagnostic messages after
: 2-3 seconds of run?
-> No, Why do you think this is a problem?

: Do you run it using ODBC interface or native driver interface?
-> The native driver.

What could be the problem?

Please advice.

1. I didn't say it is a problem I just wanted to find out whether the SP run gets aborted after returning something

2. Please try running the SP using the complete syntax as "EXEC SP_name parameters" and not just "SP_Name parameters". Also try running it using an ODBC connection. Please lete us know what you get.

: -> No, Why do you think this is a problem?
: -> The native driver.

: What could be the problem?

: Please advice.

: 1. I didn't say it is a problem I just wanted to find out whether the SP run
: gets aborted after returning something

is there a limitation in the trial version?!

: 2. Please try running the SP using the complete syntax as "EXEC SP_name
: parameters" and not just "SP_Name parameters". Also try
: running it using an ODBC connection. Please lete us know what you get.

we already use the EXEC keyword.

ODBC I don't like so much, but if you think this helps...

any other ideas? we use MS SQL Server 2000.

This is not a limitation. This is an issue with the database driver or job run-time mode. And the reason we asked to try an ODBC connection is to verify whether the driver is responsible to premature SP termination.
: is there a limitation in the trial version?!

: we already use the EXEC keyword.

: ODBC I don't like so much, but if you think this helps...

: any other ideas? we use MS SQL Server 2000.