Not that I know of, though I would bet @MladenPrajdic would be receptive to the idea of looking at including it in SSMS Tools Pack

http://www.ssmstoolspack.com/

regulars: Does...

I know Michael from another forum and have the greatest of respect for him, but I will respectfully disagree. The requirements of some systems necessarily require natural keys, for others...

Really? Three pages barely counts as a warm up for a surrogate Vs natural key thread 😉

Tom.Thomson (10/14/2010)

---

"can be used on range queries" really means "make things which are used close together live close together in the index" which, in an OLTP system, may have nothing...

Why? You have a working solution and someone working on an improved solution.

Pffft - I always said FOR XML was rubbish 😉

Oh nice, yes - definitely use that over the scalar.

I've not yet had the "pleasure" of using FOR XML in the wild.

USE test;

IF EXISTS (SELECT NULL FROM sys.tables WHERE object_id = OBJECT_ID('dbo.test_IP'))

BEGIN

DROP TABLE dbo.test_IP

END;

CREATE TABLE dbo.test_IP

(

...

Yes, I had just this second noticed that. I missed the issue with the original formatting.

It should just be a self join though. Hold on...

That will be due to the dbo.Test, whatever that is.

Apols - my bad.

COALESCE(@result + ', ', '') + dummy_column

Actually, I'm not taking it entirely off tack. My correction is born of a similar observation\ pet peeve as yours. Far too often I see primary key\ IDENTITY\ Autonumber (in...

Sorry - don't want to take this off tack, but a column defined as IDENTITY is not "guaranteed to be unique within the table". Only a unique index\ constraint (or...

That's not even correct.

Stating the obvious: I assume you can't simply have system one call system two when it has completed the loads?

Otherwise no although I would want this sort of thing persisted...