Results 1 to 3 of 3
  1. #1
    Join Date
    Aug 2005
    Posts
    55

    Unanswered: multiple stored procedure...or 1 dynamic procedure?

    Ok, so i have this program, and at the moment, it generates an sql statement based on an array of db fields, and an array of values...

    my question is this, is there any way to create a stored procedure that has multiple dynamic colums, where the amount of colums could change based on how many are in the array, and therefore passed by parameters...

    if this is possible, is it then better the pass both columns and values as parameters, (some have over 50 columns)...or just create a seperate stored procedure for each scenario?? i have no worked out how many this could be, but there is 6 different arrays of colums, 3 possible methods (update, insert and select), and 2 options for each of those 24...so possibly upto 48 stored procs...

    this post has just realised how deep in im getting. i might just leave it as it is, and have it done in my application...

    but my original question stands, is there any way to add a dynamic colums to a stored proc, but there could be a different number of colums to update or insert into, depending on an array??

    Cheers,
    Justin

  2. #2
    Join Date
    Feb 2004
    Location
    One Flump in One Place
    Posts
    14,912
    Hi freefall

    Did you read the link Jesse gave you? Read that and you shouldn't need much more tutelage on the use of dynamic SQL.

    Just FYI - you would probably find most of the people on here would say you are going the wrong way and shouldn't be looking to use dynamic SQL for this. Instead have a number of hard coded sprocs specific to the tables and actions you want to perform on the tables. This will result in more secure and efficient code that is easy to debug.

    HTH
    Testimonial:
    pootle flump
    ur codings are working excelent.

  3. #3
    Join Date
    Aug 2005
    Posts
    55
    Quote Originally Posted by pootle flump
    Hi freefall

    Did you read the link Jesse gave you? Read that and you shouldn't need much more tutelage on the use of dynamic SQL.

    Just FYI - you would probably find most of the people on here would say you are going the wrong way and shouldn't be looking to use dynamic SQL for this. Instead have a number of hard coded sprocs specific to the tables and actions you want to perform on the tables. This will result in more secure and efficient code that is easy to debug.

    HTH
    Hi,

    Yeah I did have a quick read of the dynamic sql like Jesse provided...and was able to solve the previous problem with it...as i was a bit under the pump when i read it, i did not read the entire thing, and missed anything relating different amounts of dynamic columns...

    You have pretty much answered what i was asking anyway, so it looks like im in for a long session of writing stored procs...

    Thanks Again,
    Justin

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •