I had considered a table variable but...

"Tables variables cannot be used in a INSERT EXEC or SELECT INTO statement."

http://support.microsoft.com/kb/305977/en-us

Thank goodness for old style temp tables!

The SSIS package generates a...

They both work for both 2000 and 2005 databases.

SMO has a fuller toolset, but they're both incomplete (try generating ALTER PROC scripts).  SQL-DMO is deprecated and so it won't be...

I can see the merit in keeping all databases on the same instance - you don't need to use linked servers etc.

The only pro as far as I can...

ok..so maybe you don't habla espanol...but the answer is in the sql, and sql is the universal language ;=)

As for the spanish, you could have made an effort!  Below is...

I remember reading that xsl:include isn't supported.  You'll have to stick it all in the same xsl sheet I'm afraid!

David McKinney.

Well spotted Leifah.

SELECT DATEADD(ss, 1157472771, '1 jan 1970') gives 2006-09-05 16:12:51.000

David.

Without knowing exactly what sort of problems you were having which prompted you to do the conversion at SQL level, I would suggest that you return to tackling this initial...

I've today written SMO code to 'script it all'.  I ran it on a database with 180 objects, including functions, materialised views, sprocs and loads of referential integrity.  It managed...

A good introduction.  I think it's a big and important subject, and there's not much detail on the web on this. 

Specifically I've yet to find code that will script my...

I think you need to search for Stopwords on the net.  An example I found is below.  There are different kinds of stopwords - which can be any sort of exclustion list, so you...

Thinking again about my post above...I guess there could be an issue, if 2 users have concurrently created temp tables with the same name.  You could probably end up deleting...

not sure what the 'real name' of a temp table is....I can see where you're coming from gleazenby, however the code below DOES WORK.  Just make sure you check for...

Good idea, good code....terrible name for a stored procedure!