Post reply

Using a "RunID" to push data to prod DW but not enable for reporting until later?

  • May 4, 2012 at 7:12 am

    #1483532

    sam.dahl (5/3/2012)

    Daniel Bowlin (5/3/2012)

    I have an idea for a different approach. It would take a little effort to set up, but way easier than a parallel environment.

    This is an interesting approval approach, but I'm not sure how it solves the original problem, that of having production ready data available/visible to a user for approval and yet unavailable/invisible in the actual production environment.

    I don't mean to be overly critical, I'm just interested in how you intend it to work.

    Are you providing the data-in-need-of-approval to the user via a report?

    It certainly sounds viable, but the OP will have to provide input to determine if it would work in their environment.

    My intent was to move the data into production, but have a filtering hidden or internal parameter on the production report that would show the appropriate data to the end user depending on the approval status. This obviously would depend on there being some logical way to filter the data based on the approval status such as date or time range etc. However ACinKC's comment on making the approval based on a dev environment and then have my process kick off the actual move of data to production I think is even cleaner.

  • May 4, 2012 at 1:11 pm

    #1483741

    yes, cleaner. Staging for me is simply a table of "this run" that will either become the new fact table or fails for whatever reason. Not a separate db, just a different table. Utilize partition switch to make it Prod.

    I don't require user approval, I have validation in the package. The step that does the partition switch also makes some minor checks that the loaded data "looks good".

    If I had to float this for signoff indefinitely, I'd make an approval button that fires the partition switch step (could be simple sp) and off we go, staging is live.

  • May 6, 2012 at 5:47 pm

    #1483939

    herladygeekedness (5/4/2012)

    If I had to float this for signoff indefinitely, I'd make an approval button that fires the partition switch step

    ^ This.

    EDIT:

    To elaborate: given the requirement to wait indefinately for user signoff, yet to maintain two sets of production data, the partition approach allows you keep staging simple, continue to load data incrementally, instant productionisation at the push of a button... quite elegant, your Lady Geekedness.

Viewing 3 posts - 16 through 17 (of 17 total)

You must be logged in to reply to this topic. Login to reply