>>The alternative way is to pass local cursor to the SQL Server, e.g. something like this
>>text to lcInsert noshow
>>declare @LocalTable (field1 varchar(10), field2 int)
>>endtext
>>
>>select local cursor
>>scan
>>
>> using textmerge create insert statements for the local cursor
>>endscan
>
>Does that @LocalTable remain in the Sql Server database afterwards?
>
>And, what if you have multiple users doing this process at the same time? They will all be trying to use the same @LocalTable and the records would get all jumbled up.
>
I am using table variable, so it doesn't remain in SQL Server - once the batch finishes execution, it is removed. If I would use a temporary table, it may remain.
If it's not broken, fix it until it is.
My Blog