Note that COMMIT statement will not execute if there is no data in @TableToBeCleaned satisfying the where clause.

Change the fourth line as

SET @STR = @STR + 'COMMIT ' +...

Have you tried enabling IIS log with extended log format and analying the log.

This might give some idea on pattern from which this error is getting generated.

One more difference between EXEC and sp_executesql is that first one does not allow you to run parameterized queries.

sp_executesql allows you to parameterize the sql and inturn helps in caching...

Append to media option allows you to keep multiple backups on the same media.

For example, if you back up every day in a week with append to media option,...

If I understand correctly, you are asking about printing a document inside a stored procedure.

This can be achieved using SP_OACreate to create a word object and then issuing a print...

One alternative is to use SQLDMO. The Database object in SQLDMO has a GenerateSql Method which generates the scripts for all objects in database.

You can write a vb program...

This means to me as below

The sql*server service is running under local system account(control panel-->Administrative Tools-->Services) .

Naturally, this local system account will not have any rights on the network...

I forgot to mention that to raise a custom error you can use RAISERROR statement

One way to trap the error is to use the @@ERROR global variable in the stored procedure.

for eg.,

INSERT INTO tableA Values (1,2,3)

SET @m_err =...

One alternative is to copy the data to a temporary table before modifying the structure, modify the structure of original table(Drop & Create), Issue INSERT INTO SELECT to repopulate the...

One way is to use recursive functions

Sql*server 2000 supports user defined functions.

You can create a function fn_IsValidChild with two parameters projid and parentid. This finds the parents for projid...

This can mean two things.

1. The trigger is not getting called at all on modification to table(insert/update).

2. The trigger gets called but it does not do anything.

Since you have mentioned...

This is regarding mahgoub's second query

<<However, I am running concatenated SQL queries from within VB and the program typically runs for 1-3 days>>

I am not clear on this. Let me...

This is with reference to mahgoub's first query regarding releasing memory when using QA.

There is a option to clear the unreleased memory without restarting Sql*Server

DBCC FREEPROCCACHE

DBCC DROPCLEANBUFFERS

The first one releases...

It looks to me like ASP script time out and not database time out.

In any case the following might help

There can be two kinds of timeout in web application....