Posted by MikeJ on 07/26/07 22:11

thanks for your response
MJ

"Roy Harvey" <roy_harvey@snet.net> wrote in message
news:uhtha398sc8vocro8ib3mga29a2lbhj7v1@4ax.com...
> If I had to choose just one it would have to be SELECT simply because
> there are times SET will not do the job.
>
> One more point that I did not see coverd in the article linked by
> Jason. It is common to want to retrieve both the @@error and
> @@rowcount values resulting from a command. To get both and save them
> to @variables (commonly @error and @rowcount) you MUST use SELECT, as
> the @@values are destroyed by the first command that retrieves them.
>
> I use SET to assign a constant, or perhaps increment a counter, but
> use SELECT when the data comes from a query or is otherwise more
> complicated. But I don't pretend that is "best practice", as I don't
> believe there is a clear best here.
>
> Roy Harvey
> Beacon Falls, CT
>
> On Thu, 26 Jul 2007 10:59:17 -0700, "MikeJ"
> <vettes_n_jets@sbcglobal.net> wrote:
>
>>hi...i would like to know best practice when assigning a value to a
>>variable
>>example below
>>
>>set
>>or
>>select
>>
>>declare @var1 varchar(25)
>>set @var1='abc'
>>select @var1='abc'
>>
>>to me
>> set is implicit
>> select implies conditions
>>
>>i see both used all over the place here at my new company....
>>so witch is better practice
>>
>>tks
>>MJ
>>
>>

[Back to original message]