I forgot to add, your temporary table structure has to match the sp_help_job returned recordset structure.

sp_help_job is in the msdb database therefore change you statement to

insert #tblJob (job_id, current_execution_status)

exec msdb.dbo.sp_help_job @job_name='jobname', @job_aspect='JOB'

I think you mean SELECT INTO.

I don't know because SELECT INTO is on my list of "avoid like plague" constructs.

It has huge performance overheads which is why I never use...

I seem to remember that Steve or Andy had a problem where accessing the first 9000 rows of a table was OK, but anything after that produced errors.

The solution was...

If you know the structure of the recordset returned by a stored procedure then you can build a temporary table of the same structure.

For example, let us suppose that my...

You can't write extended stored procedures with VB.

They require specific function calls that are not supported in VB.

The last time I checked C++ and Delphi were the main languages for...

Look on the bright side guys, we have to put up with Tony Blair.

CAST and CONVERT cause syntax errors in Index Server.

Index server SQL looks like "proper" SQL, but as I said, it seems to leave out all the useful bits!

If you look on the Microsoft SQL Server site you will see that there is a books on-line update dated January 2004.

You can tell if you need the update by...

Return values are integers.

Alter your stored procedure and read the recordset returned from the stored procedure.

CREATE PROCEDURE test @log_id as int

AS

SET NOCOUNT ON

select solution from dbo.tbl_mis_log where log_id=@log_id)

GO

I've found srv.h in the examples file and it looks considerably different to the one in the visual studio directories.

Temporarily I have replaced the vs version with the ODS version...

Marvellous isn't it.  Bet it happened in a busy period as well!

I've had it happen to me and the only thing I could do was rebuild the server, reinstall SQL...

Unfortunately this is one of the problems with user defined datatypes.

You can update them, but they don't affect existing definitions within tables.  They act as a template at the time...

SELECT TOP 25 * FROM Products WHERE ProductID NOT IN (SELECT TOP 25 ProductID FROM Products ORDER BY ProductID) ORDER BY ProductID

Presumably this was for the Northwind database?

SET FMTONLY on

GO

USE...

Interesting point this.  An unscrupulous supplier could come up with a dodgy QOD on purpose!