you can only do this with dynamic sql.  seems like a bad idea to me though. 

basically you'll be executing arbitrary sql blindly.  anyone with access to this table could...

it's not BULK_INSERT, but BULK INSERT, without the underscore.

also BULK INSERT is one-sided: there's no BULK EXPORT.  so you have to use bcp...

one view will NOT solve all the problems that EAV creates however. 

Yes.  Maybe I forgot to mention that scriptdb.exe uses SMO. 

In fact, all of SSMS is built on top of SMO, just as EM...

ok, but there are things in even everyday objects that DMO won't know how to script properly, such as indexes with included columns, tables that use CLR types for a column, etc. ...

I forgot to mention that for scriptdb.exe, the source is freely available so you can modify it as you see fit if it doesn't meet your needs as is. 

It's implemented...

that's to be compared with this query, which is what you would have had if not using EAV:

select FirstName,Lastname,CompanyName,UserID from User

which do you prefer?

a great example of the headaches the EAV model causes. What should be a simple select turns into a messy pivot. What do you do if you need...

DMO is deprecated - if you use DMO you won't be able to script objects in 2005 that don't exist in 2000, such as assemblies, etc.

for a free tool, one thing you could do is generate scripts for both schemas using this:

http://www.elsasoft.org/tools.htm

and then compare the result with windiff or similar.

this free tool will script out all objects in any 2000 or 2005 database, using SMO. source is available so you can modify it as you please.

it's very useful...

You might want to check this out. it will generate scripts for ALL objects in any 2000 or 2005 db, a separate file for each. it's useful for...

Here's a free tool I wrote to generate scripts against any 2000 or 2005 database. Very useful for getting all your objects under source control.

http://www.elsasoft.org/tools.htm

for importing/exporting large amounts of data from/to flat files, I use bcp.exe.

see "bcp utility" in BOL.

if you are importing a significant fraction of the current table size, it's a good...

here's a good explanation of hash join:

http://blogs.msdn.com/craigfr/archive/2006/08/10/687630.aspx

Craig Freedman's blog is excellent for learning about the inner workings of the optimizer.