July 13, 2010 at 11:33 am
As far as I can tall, there's no way to pass a table or table variable as a parameter.
Is passing in XML and parsing it really the best way?
I guess my issue is I *want* to do some bulk inserts, but engineering requires that we do everything through their procs. The procs are designed to modify one row at a time and it can take hours for what I want to do looping through a cursor to call their procs when a simple update command would take under a second.
Anyway, I need to create a store proc that is entirely contained, so it must only work with the parameters passed in and/or the standard tables. I need to pass in my dataset as a variable, but converting my updates into XML makes for 5MB-10MB varchars and that just seems messy.
Is there a better way to pass in a large dataset?
Thanks 🙂
July 13, 2010 at 11:47 am
July 13, 2010 at 8:51 pm
Here's an article on passing data as if it were a 1, 2, or 3 dimensional array...
http://www.sqlservercentral.com/articles/T-SQL/63003/
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply