Okay, just one note on GUID as keys (from BOL)

At 16 bytes, the uniqueidentifier data type is relatively large compared to other data types such as 4-byte integers. This means...

Sorry, but isn't a Social Security Number uniquely enough?

Don't use float. It's imprecise by nature.

I would use decimal as this is an ANSI standard datatype.

Search the script section here, I bet you'll find something useful. Your problem seems to be nothing exotic.

What are you trying to do? Maybe there is a way to avoid a Cursor and a UDF.

Not that I know too much about DTS. But this looks like a problem with your original data like the error message says. You might want to take a look...

Yeah, you're right!

With a correction in the typo; it's INFORMATION_SCHEMA.SCHEMATA

For databases you can fire

SELECT * FROM MASTER..SYSDATABASES

For the rest take a look at the INFORMATION_SCHEMA views in BOL. Especially INFORMATION_SCHEMA.TABLES and INFORMATION_SCHEMA.COLUMNS.

Also worth searchgin is the script section...

Thanks for the links. I'll try them now

The 26 should be just for demonstration purposes. DBCC OUTPUTBUFFER requires a systemprocess ID as input parameter.

You might want to take a look at both DBCC OUTPUTBUFFER and SPID...

Not quite sure, but this might be what you are after

http://www.nigelrivett.net/spFormatOutputBuffer.html

To add to SQLBill you might find Tom Moreau and Itzik Ben-Gan's 'Advanced T-SQL' book useful.

Personally I think it's better than Henderson's one.

Frank.........I've been offline for awhile with a job change. Good to see you lurking out here. The client is probably going to have to do this, but...

One thing that comes to mind are the sp_OA* procedures. But they certainly have a huge downside.

What about doing this at the client?

I like the wizard! It is a good starting point. It builds the foundation you can go further on. Once you've built your indices, it's up to you to monitor...