IF you do the following you will NOT get ---------

PRINT @Counter v. SELECT @Counter

1.  No new instance is needed.  All you need to do is give different name and away you go...

Should be no problem to...

Change from SELECT ... to PRINT.  Of course this will only accept a single PRINT value thought.....

As far as I know this cannot be done.  The color is a return to screen feature only.  I don't know of a 3rd party tool either that will accomplish...

Why not BACKUP/RESTORE it using a different name?

Unless you have defined one then there is no audit trail of who/what/where/how/why..

The problem is:

SQL is looking at your passed variable 1,2,3,4,5 as a LITERAL and NOT a NUMERIC ARRAY.

What you want to do cannot be accomplished by what you are trying to...

SQL doesn't supply built-in tracking.  You need to supply the audit trails, etc..

see same post http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=92&messageid=171994 for reply

For #1 I would ensure that the security of your server is set in mixed mode and not windows mode only. SQL security tab under properties when you right-click on...

I remember having a conversation with someone here that stated local variables do perform better but can not remember why...

How are you defining the variables?  VARCHAR v INT?

How are you...

How are you correlating C to S?

Believe it or not this happened to me the other day and this looks as good a place as any to post:

I went to a DBA at the place where...

Taking it one step further you can even have COLUMNAR collations in the SAME table be different from each other AND the database

In addition IF you don't want NULL to be added Why not...

CREATE TABLE #TEMP

(FieldX VARCHAR(10) NOT NULL DEFAULT(''))

This way the program will scream if it gets a NULL