I would also go for the backup/restore method but make sure that you transfer logins first, otherwise you will get broken users.

If your two servers have different sort orders, code...

If you have a view then you can only use ORDER BY statements if you use the SELECT TOP 100 PERCENT version.

Personally I am not ecstatic about anything that involves coding logins and passwords into stored procedures.

If you use sp_helptext on a stored procedure you get all the code for the...

You need all of them.

If you don't know what the structure is i.e. is notify_level_eventlog an int, smallint, byte it doesn't matter because SQL is intelligent enough to do an...

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...