Frankly no... I usually try to find the fasted query for a situation... and often 2 versions can have the same performance. Maybe someone else might think of one.

If the any of those tempdb tables are locked (sysobjects, syscolumns, sysindexes, sysindexes), any code that needs to create a temp table or even a table variable will not be...

Generally, this is something that will change between each call from the app .

Do you have a specific case?

This is one of those "it always depends" .

Why can't you use this syntaxe? : Form_FormName.fkClientID = id

Here's my thinking : Don't use cursors, ever. Then if you find a situation where a cursor is faster than a set based approach or there's no set based...

What is SAP short for? Yahoo doesn't return anything usefull.

As I said, not the expert in this matter . Thanx for correcting my answer David.

How about finding 3 other ways then .

Thanx Shown for this input, but I'd like to stress out that these methods are only LAST RESORTS, you must first try to find the SET BASED approach...

Can't you try it like this?

Select * fro LinkedServerName.DbName.dbo.TableName where ...

/*this creates a sequence table*/

CREATE TABLE [Numbers] (

[PkNumber] [int] IDENTITY (1, 1) NOT NULL ,

CONSTRAINT [Pk_Number] PRIMARY KEY CLUSTERED

(

[PkNumber]

) ON [PRIMARY]

) ON [PRIMARY]

GO

Declare @i as int

set @i = 0

while...

Now that's what I was talking about in the other post .

Arrays and Lists in SQL Server - Slow

StmtText ...

I know .

My bad, I thaught you were writting the split code...