What datatype is ColD? Is it a computed column? Persisted?

Or use the new OUTPUT operator?

CREATE TRIGGERTR_YOURTABLE_STATUSCHANGED

ONYOURTABLE

AFTER UPDATE

AS

INSERTSomeStatusTable

(

STATUS,

FORMID,

DATECOMPLETED

)

OUTPUTi.INVOICEID,

i.FORMID,

GETDATE()

INTOShippingQueue

(

INVOICEID,

FORMID,

DATEQUEUED

)

SELECTi.STATUS,

i.FORMID,

GETDATE()

FROMINSERTED AS i

WHEREi.STATUS = 3

AND i.FORIMID = 6

--get next available id

UPDATE Ids SET @NewId = lastid = lastid+1 WHERE tablename ='EventLog'

if...

Last_Name like COALESCE(@Last_Name, '') + '%'

Maybe "beyond relational" should be read in the context "relational and more" ?

Also asked and answered here

http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=116600

Better DateOnly and TimeOnly algorithms.

DECLARE@Sample DATETIME

SET@Sample = '2008-10-22 11:41:36.920'

SELECTDATEADD(DAY, DATEDIFF(DAY, 0, @Sample), 0) AS DateOnly,

DATEADD(DAY, DATEDIFF(DAY, @Sample, 0), @Sample) AS TimeOnly

DECLARE@Sample TABLE

(

pk INT,

dat VARCHAR(20)

)

INSERT@Sample

SELECT4, '1' UNION ALL

SELECT2, '00102' UNION ALL

SELECT6, '11' UNION ALL

SELECT1, '001' UNION ALL

SELECT3, '0102' UNION ALL

SELECT5, '100' UNION ALL

SELECT7, 'R00102'

-- Peso

SELECTpk,

dat

FROM@Sample

ORDER BYPATINDEX('%[^0]%', dat) DESC,

CASE

WHEN dat LIKE '%[^0-9]%'...

And what is the expected output based on your sample data?

Not even with SQL Profiler?

You can get every statement within the function there.

It is a sign that the...

A solution for normalized tables would be

DECLARE@qh11 TABLE

(

Serial INT,

qh11 VARCHAR(1)

)

INSERT@qh11

SELECT1, '2' UNION ALL

SELECT1, '3' UNION ALL

SELECT1, '4' UNION ALL

SELECT1, '5' UNION ALL

SELECT1, '6' UNION ALL

SELECT1, '7' UNION ALL

SELECT1, '8' UNION...

A solution without use of auxiliary table such as a tally table is this

;WITH Yak (Serial, qh21, c, n)

AS (

SELECTSerial,

qh21,

SUBSTRING(qh21, 1, 1),

1

FROMIndus

UNION ALL

SELECTSerial,

qh21,

SUBSTRING(qh21, n + 1, 1),

n + 1

FROMYak

WHEREn <...

ONLINE = { ON | OFF }

Specifies whether underlying tables and associated indexes are available for queries and data modification during the index operation. The default is OFF.

Note: ...

I guess you could use the ONLINE hint, but it requires the Enterprise edition to work.

The ONLINE hint determines whether concurrent user access to the underlying table during operation.

See http://msdn.microsoft.com/en-us/library/ms186241(SQL.90).aspx

and...