locked
What is Alternative of numbered_procedures? RRS feed

  • Question

  • Hi every body

    I use numbered_procedures because of versioning purpose. (Notice: versioning means version of live and up procedures and Doesn't mean source control purpose)

    But unfortunately Numbered procedures are deprecated.

    Please help me what can i do now?




    • Edited by Hamid309 Saturday, January 19, 2019 6:16 AM
    Saturday, January 19, 2019 6:14 AM

Answers

  • Here's an idea. Write a wrapper procedure that takes the regular parameters plus a version number. then it calls the correct one of the differently-named procedures. That way you can have API/application code that only has to deal with one procedure name, and a configuration variable can handle which version of code a given client runs.

    Dan Jameson
    Associate Director of IT/DBA
    Children's Oncology Group
    www.ChildrensOncologyGroup.org

    • Marked as answer by Hamid309 Sunday, January 27, 2019 1:54 PM
    Thursday, January 24, 2019 4:48 AM

All replies

  • versioning means version of live and up procedures

    What specifically does "live and up" mean?


    Dan Jameson
    Associate Director of IT/DBA
    Children's Oncology Group
    www.ChildrensOncologyGroup.org

    Saturday, January 19, 2019 8:13 AM
  • Customers is using that versions now.

    For example, customer A  use MySP ver 1 and Customer B use MySP ver 2.

    previously I named that procedures Like This:

    dbo.MySP_Ver01

    dbo.MySP_Ver02

    Now I use this convention:

    dbo.MySP;1

    dbo.MySP;2

    Some customers use dbo.MySP;2 and anothers use dbo.MySP;1 until they migrate to dbo.MySP;2

    Saturday, January 19, 2019 8:34 AM
  • Customers is using that versions now.

    For example, customer A  use MySP ver 1 and Customer B use MySP ver 2.

    previously I named that procedures Like This:

    dbo.MySP_Ver01

    dbo.MySP_Ver02

    Now I use this convention:

    dbo.MySP;1

    dbo.MySP;2

    Some customers use dbo.MySP;2 and anothers use dbo.MySP;1 until they migrate to dbo.MySP;2

    what is different between MySP;2 and MySP;1 in your case? combination of parameters?

    Please Mark This As Answer if it solved your issue
    Please Vote This As Helpful if it helps to solve your issue
    Visakh
    ----------------------------
    My Wiki User Page
    My MSDN Page
    My Personal Blog
    My Facebook Page

    Saturday, January 19, 2019 9:45 AM
  • We have 2 scenarios

    1.different combination of parameters

    2.different body of procedures with same input parameters (like: change calculate method and etc )

    we use this scenarios in banking industry, we change some business logic base on new regulatory compliance and change our procedures without changing their names.

    but some banks are selected as a pilot and test, therefore we need 2 versions of procedures.

     

    Saturday, January 19, 2019 10:07 AM
  • Since numbered parameters are gone, your option is to go back to have different names...

    Tibor Karaszi, SQL Server MVP (Web Blog)

    • Proposed as answer by Puzzle_Chen Thursday, January 24, 2019 7:26 AM
    Tuesday, January 22, 2019 10:30 AM
  • Here's an idea. Write a wrapper procedure that takes the regular parameters plus a version number. then it calls the correct one of the differently-named procedures. That way you can have API/application code that only has to deal with one procedure name, and a configuration variable can handle which version of code a given client runs.

    Dan Jameson
    Associate Director of IT/DBA
    Children's Oncology Group
    www.ChildrensOncologyGroup.org

    • Marked as answer by Hamid309 Sunday, January 27, 2019 1:54 PM
    Thursday, January 24, 2019 4:48 AM
  • Tanks

    I will try your solution.

    best regards

    Sunday, January 27, 2019 1:53 PM