First of all thanks to every one for putting your valuable comment.
Jack Corbett (8/25/2009)
lafleurh (8/25/2009)
In the theoretical sense, it should not be necessary to insert multiple rows in one command (as stated above). But in the practical sense, we have had to do this. The number of round trips to the database (for us) greatly affected performance.Our technique (for MS SQL Server and Oracle) is not discussed here. We generate Insert statements and concatenate them into a string and execute them using an ADO.NET command object. It reduces the number of round trips to one--and it works.
Sure that will work, but it also opens up the server (SQL Server and Oracle) for SQL Injection. What are you doing to reduce that risk?
I just wanted to add one more point, the application where we implemented these techniques is mainly using JAVA family technology and data can only be handled through SP no Inline query .
mbrunton
I'm not sure that is true. We use varchar(MAX) to pass comma delimited strings. I believe these are up to 2GB
No, even if you use varchar(max). It will hold 4000 / 8000 characters max including the delimiter character.
Please check the Part-I forum, where I posted the testing script.