- Admin
- #1
this thread provoked my question:
also, i apologize if this is nothing but a demonstration of my newbie-ness in SQL...
am i the only one that thinks a series of INSERT statements to submit many rows of data is a little insane?
say i want to add 100 new authors to a table i'd much rather call some sort of stored procedure to do this all in one fell swoop then to make 100 round trips to the DB.
that's where CLR Stored Procs come in.* i've never tried them, but from what i know this will allow me to just pass a List to the database to preform all the inserts right on the server, correct?
More...
View All Our Microsft Related Feeds
also, i apologize if this is nothing but a demonstration of my newbie-ness in SQL...
am i the only one that thinks a series of INSERT statements to submit many rows of data is a little insane?
say i want to add 100 new authors to a table i'd much rather call some sort of stored procedure to do this all in one fell swoop then to make 100 round trips to the DB.
that's where CLR Stored Procs come in.* i've never tried them, but from what i know this will allow me to just pass a List to the database to preform all the inserts right on the server, correct?
More...
View All Our Microsft Related Feeds
