Lots of useful ideas here:

http://groups.google.de/groups?hl=de&lr=&threadm=119001c4a5c5%24c140b440%24a601280a%40phx.gbl&rnum=1&prev=/groups%3Fq%3Dconvert%2Bfrom%2Bhexadecimal%2Bto%2Ba%2Bdecimal%26hl%3Dde%26lr%3D%26selm%3D119001c4a5c5%2524c140b440%2524a601280a%2540phx.gbl%26rnum%3D1

Have you try with STR() yet?

This works for me:

ALTER TABLE Orders ADD testME VARCHAR(30)

GO

USE NORTHWIND

GO

UPDATE Orders SET testME = 

 CONVERT(VARCHAR(10), OrderDate,101) +

 ' ' +

 STR(Freight,2 ) FROM Orders WHERE OrderDate...

Who knows?

What is a "high insertion rate"? for you? How will this happen? The simple number of rows is quite handable.

I'm sure you have pretty good reasons for this intentional denormalization, don't you?

Anyway, as Remi already mentioned, if you don't care about truncation...

Okay, another variation:

SELECT

 DATEADD(MONTH,DATEDIFF(MONTH,30,GETDATE()),0) FirstDay

 , DATEADD(MONTH,DATEDIFF(MONTH,30,GETDATE()),30) LastDay

Interestingly you need to check BOL for IDENT_CURRENT to find out, why SCOPE_IDENTITY() is mostly preferable to @@IDENTITY

A great place to start is to read Brian Kelley's article on that topic:

http://www.sqlservercentral.com/columnists/bkelley/allarticles.asp or visit http://www.sqlsecurity.com 

Here are some more links:

http://msdn.microsoft.com/msdnmag/issues/04/09/SQLInjection/

http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sp3sec03.mspx

That will most likely be the day I stop using SQL Server and make the move to Oracle.

...

where

T1.Key *= T2. Key and

T1,Key *= T3. Key.

Do a search in any SQL...

I don't think this is undocumented. This technique is called aggregate concatenation and widely used. However, there do exists problems with it which are described here:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;287515

Please pass on the exact query for it

I'll leave a bit of work for yourself, okay?

Either try searching the site here for some...

Have you tried truncating the child tables first and then the parents?

Aargh, sometimes you can't see the wood for the trees:

SELECT

 t1.location

 , RIGHT(STUFF(CONVERT(CHAR(22),t1.EntryDate,13),21,4,' '),9)

 , CASE

    WHEN DATEDIFF(mi,t1.EntryDate,t2.EntryDate)>1440

    THEN DATEDIFF(mi,t1.EntryDate,t2.EntryDate)-1440

    ELSE DATEDIFF(mi,t1.EntryDate,t2.EntryDate)

   END

FROM

 #test t1

JOIN

 #test t2

ON

 t1.location = t2.location

AND

 t1.EntryDate <...

Actually it's no question of if, but rather when MS will discontinue. See if this helps explaining: http://www.microsoft.com/sql/techinfo/tips/development/July23.asp

May I add that this might turn out a phantastic occasion to explore the collected wisdom of the SQL Server Books Online (aka BOL, aka the online manual)?

Never mind.

FWIW. Note the CASE expression to take care of period greater than 1 day:

IF OBJECT_ID('#test')>0

 DROP TABLE #test

GO

SET NOCOUNT ON

CREATE TABLE #test

(

 ENTRYDATE DATETIME

 , [name] VARCHAR(10)

 , Location INT

)

INSERT INTO #test VALUES('2005-01-01 10:00:00', 'Customer1',...