Copy Functions between Databases in the same SQL server Answered

Tacio Aurelio Alves

I have several databases in my server, for different countries (like 20). We use to have an old addon to control our core business. We are migrating all the function of this addon to B1UP functions. But now we are facing an issue because every little change, we have to export the functions, enter in each database, and import the functions. 

I was wondering if we can create something to improve that. I imagine two possible solutions:

1) create a package with the functions (as exporting everything like we already do) but then have a tool to import/update in several databases at the same time.

2) When creating a function/validation/item placement, has a option to mark this function as GLOBAL. This will trigger to have a unique code for it, and a tool to copy across the databases.

 

We are suffering so much with this today!!!

Comments

4 comments

Date Votes
  • Comment author
    SSP Automation
    Thank you for your request. It has been scheduled for review by the development team that will get back to you should there be questions.
    (Please note that as we are user-driven we can't guarantee that your request will be met unless it gets many votes and/or fit the product vision)
    Read more about the Feature Request process here
    [Internal Id: 19354]
    0
  • Comment author
    Rasmus Jensen

    Hi Tacio and thank you for the request.

    This is a real though one that have come up a few times before over the years.

    There are two core reasons why this is not currently in the current offering:

    1. Is percentage of installations that could benefit is quite slow as most people do not have many databases or if they have, they do no have a unified set of features like it seems you have here.
    2. If we are to do it, we want to do it right and that makes this a big undertaking. What I means is that for this global copy to work we need uniques codes for everthing even down to line level, but on top of that we also feel the need for a global unique mapping system (say you have a Macro that set a BP Group using the BP group code... These codes are from SAP and auto-generated in each database so it might be code 100 in one database and code 103 in another and we feel a solid system should also be able to handle this... We did a deep analysis of how to do this several years back, and the result of that study was that this task was a 600+ man-hour task to make... Given the level of features back then compared to now, that estimate is roughly guessing closer to 1000+ man-hours to implement if we are to do it right :-/

    So we stand here with a big big task that at the same time give little value to most installations out the (I'm not saying this would not bring you great value, it would, but as a general feature it would not)

    ***

    But lets have an open discussion: Anyone/how many out there need the same as Tacio? And would a simple raw code be enough in your opinion not caring about ids/codes and small difference in need feature across the different database (aka is our suggestion of how it need to be done over-engineering)?

    0
  • Comment author
    Tacio Aurelio Alves

    Thank you Rasmus, ok, I understand your points.

    Maybe start by a new function to massively import a package accross databases, like we have the MASTERDATA generator tool, overriding functions, is a start.

    0
  • Comment author
    Tacio Aurelio Alves

    I found one more here: 

     

    https://support.boyum-it.com/hc/en-us/community/posts/360037175153-Multi-database-company-B1UP-Module-Sync?page=1#community_comment_360001801777

    0

Please sign in to leave a comment.