Thought I'd post something folks can play with... could easily be turned into a proc... can be easily modified for an Insert/Values instead of an Insert/Select. With a little forethought,...

Nigel Rutter (10/4/2007)

---

Doesn't need to use a cursor, it can be replaced by:

SELECT @InsertQuery = @InsertQuery + column_name + ',' from ##Temp_Generate

Hope Jeff M doesn't see...

dobrzak (4/6/2006)

---

I don't think that it is possible with sp_MSforeachtable, but why don't use systems table, eg.:

SELECT object_name(id), rows

FROM sysindexes

WHERE indid...

SELECT @@VERSION

Then, check the Microsoft site for the build number...

That nice little cross-join you included as a derived table sure did the trick.

Now, that's what I'm talking about! Nice job, Kirk!! And, thanks for posting your solution! 😀

You bet... thanks for the feedback, Greg.

No, no... Unless I'm totally misreading this, a good ol' fashioned partitioned view will do all of that without the overhead of triggers and the extra table. It'll be...

You don't? :blink: There's an example of what the input file looks like, what the table looks like, what the BCP format file looks like, and what the...

See attachment... 😉

Yeah... that's it...

Yeck!

No, no.... the overhead of a cursor is not required here. Take my previous suggestion and find out how to build a recursive CTE to resolve these types of...

Sorry folks... I didn't check...

Heh... thanks, Marcus. Most folks keep that type of info in two separate columns...

So, are you all set or do you still need help?