Can do...

 SELECT FieldID,

        MIN(CASE WHEN FieldName = 'NAME'    THEN FieldValue END) AS NAME,

        MIN(CASE WHEN FieldName = 'Address' THEN FieldValue END) AS Address,

        MIN(CASE WHEN FieldName = 'ZIP'    ...

One more thing!  Don't even think of using the SELECT/INTO/RENAME method if others are updating the table at the same time or inserting new rows.... YOU WILL LOSE...

Almost forgot... does the table being updated have any triggers?  That really make things slow for this big an update especially if those triggers are writing to audit tables or...

Yup, I'd lose the OUTER JOIN if an INNER JOIN will do.  Also, like someone else asked, "What is slow"?  I normally shoot for about 500,000 rows per minute (sometimes...

Very, very cool...  ol' Itzik did a neat job on this one.

Ken, do you know of a fn_DecToBase function in a similar vein by anyone?

Get the list of database names from Master.dbo.SysDataBases... build your own loop or (yeeach!) cursor to step the the DB names or ID's as the outer nest for sp_MSForEachTable.

Brilliant use of recursion guys!  Absolutely awesome.

Take a look at the SQL portion of w3schools.com.  It won't teach you all of the nuances of MS-SQL Server but it will give you a nice comfortable start on...

The original requester pointed out the he wanted to do it without a cursor.  As David pointed out, the underlying code for sp_MSForEachTable and other similar routines are riddled with...

The "INTO" clause of SELECT/INTO creates the temp table on the fly. 

You are correct about COALESCE... It does the work... you could replace it with ISNULL and the effect...

As Kenneth suggested, ISNUMERIC may not cut it.  It allows for seemingly non-numeric characters such as "d", "e", and "." so that it will support scientific and exponential notation.  Continuing Sushila's...

Roger that... I'll put mine in a UDF   Thanks for the tip on the deterministic thing.

________________________________________________________________________________________________________________________

Does NOT require TimeIn/TimeOut be on same day... only requires that for every TimeIn, there is a TimeOut and that there are no "straggler" TimeOut's from the previous...

--===== Create a function to concatenate orders by customer

 CREATE FUNCTION dbo.ConcatOrderNum (@pCustomerID AS INT)

RETURNS VARCHAR(8000)

AS

BEGIN

        DECLARE @oResult VARCHAR(8000)

         SELECT @oResult= COALESCE(@oResult+',','')+OrderNumber

           FROM Customer_Orders WITH (NOLOCK)

          WHERE CustomerID...

Serqiy,

This too, is deterministic and a bit easier on the eyes...

RIGHT('000'+CAST(XID%1000 AS VARCHAR),3)