Old School:

loop through all SP's

  exec sp_helptext 'proc name'

  search text

  break (when found)

end

For future reference & a little bit of old school:

create <tablename>(<fieldname> Nvarchar(1000))

grant all on <tablename> to public

EXEC master..xp_cmdshell "bcp DB..<tablename> in C:\<filename>  /U<user> /P<password> /n"

Now you have...

data structures should be sepperate, when any of your field data in a table is repeated.

example like patient record

is linked to more than one address, & treatments, & appointments, etc... so...

You need a sequential aproach:

because you start a transaction and do all the processing in the same transaction, the flag is being set at the end of your process...(commit)

other calls start...

You need SOAP & SQLXML:

see (RE: Soap RPC via SQLXML

Posted 3/16/2004 9:39:00 AM) from fhanlon user.

You're both right & now have the requestor re-thinking the purpose for his question...

I would like to know why he/she needs to do this action and if it is a fast fix...

I believe this needs "DECLARE <name> INSENSITIVE CURSOR FOR";otherwise its not in a loop...

Insert Into @temp

  Select Distinct employeeid

  From directory

  Where higmanagerempid =...

Simple answer & most overlooked;is that you can create a trigger for each event like this:

CREATE TRIGGER [sp_INS_trrequest] ON [dbo].[TrRequest]

FOR INSERT

AS

BEGIN

CREATE TRIGGER [sp_UPD_trrequest] ON [dbo].[TrRequest]...

A large procedure is memory intensive; lots of temp tables means lots of memory allocation; Intermittent errors caused by reused memory area, like partitioning between functions. Something gets dropped, usually...

This may seem to simple, but why not place 'FETCH ABSOLUTE @FromRec FROM cPartners' into a loop?

DECLARE @MaxRec Int

SET @MaxRec = 10

WHILE (