You are welcome 🙂

You can just do a 'RETURN' at the end of the stored procedure. Assign correct value to the OUTPUT parameter and it will be passed to the calling procedure.

There is no built-in function in SQL Server 2000/2005. (in 2008, you can use the DATE data type).

You can strip off the TIME part from a datetime value by running...

The return value of a stored procedure is INT. You cannot return a string or other data types. The correct way to do this is to use an OUTPUT parameter.

You only have two CREATE statements in your script and the first CREATE statement already has it.

Now find out the missing place 🙂

Try this script and see if you get the same results:

CREATE PROCEDURE innerproc as

select 0

go

create procedure outerproc1 as

execute innerproc

go

create procedure outerproc2 as

execute innerproc

go

sp_depends innerproc

/*

name ...

which version of SQL Server are you working with? I have heard that some times the dependency information is not updated correctly. But i could not experience such a case...

SET ANSI_NULLS and QUOTED_IDENTIFIER to ON before the create statement and see if that fixes the problem.

Look for the following in BOL

DBCC INDEXDEFRAG

DBCC DBREINDEX

I agree with you Jeff. I am not in favor of using 'SELECT *'

Agreed. But in such cases, having an index (even if it is NC) might be better than not having an index (even if there is an RID lookup). An index...

Well, if the selectivity is high, query optimizer might use an 'index seek' even if the query contains "select *".

Two things

1. to retrieve the context_info value you assigned, you should use the CONTEXT_INFO() function.

2. Context_info is a binary value. you should use a VARBINARY(128) column to store it.

Here is...

Brian,

The XML parameter has the 'items' node.

Try to run the sample code (last example) in the pubs database and see if you get a correct RSS feed generated.

Is this question to me or to "bjoern"?