Sorry, yes you are correct.  It seems that until the "GO" sql server doesn't stop to make the ddl change so you are stuck with naming the columns.

ron

Try putting a "GO" just after the ALTER table statement.  It should work ok after that.

 ALTER TABLE #temp DROP COLUMN ProjectID

 GO      <-----

 SET @i=0

ron

Just in case you want a general soulution to the padding problem you can try this if you ever have a need.

declare @month as varchar(10)

set @month = datepart(month,...

However, now I'm also getting an error message from SQL Server which says:

Warning: Null value is eliminated by an aggregate or other SET operation.

What does that mean, and what...

Also, please note that if your DateReferred contains date and time values you will need to change that statement to:

And r.DateReferred >= '2005-11-1' And   r.DateReferred < '2005-12-01'

Otherwise you will miss records...

In some cases the called procedure will fail and NOT set the return code at all.

So you need to be careful.  If your @return_code was 0 before calling a stored...

I found this note in Books online but I didn't see anything on how to resolve this situation.

Note  If backing up the log...

You might want to try posting in the "Backups" forum.  I'm sure you'll get some answers there.

This is not one of my best areas but if you could tell use whether your recovery mode is set for Simple or Full backups I'm sure that will help...

Similar to the answer above, I record the spid and login_time from master..sysprocesses when recording the locking info.

Anytime I create a new lock I first delete all lock entries where...

The error handling in sql server 2000 is not very good and there may not be a reasonable way around your problem.  The only other thing I can think of...

In testing I noticed that as you stated you can't trap the error but at the same time the stored procedure does NOT abort.  If you don't test for the...

Ten years ago I don't think the truncate feature exisited (sysbase).  I gave up looking.  Sergiy, thanks so much for posting.  I wonder how long the truncate feature has been...

Oh no, Remi say it isn't so.

This (very long) article explains the new isolation levels in sql 2005.  Using SNAPSHOT should eliminate the problem.

http://www.microsoft.com/technet/prodtechnol/sql/2005/SQL05B.mspx

ron