Skip to main content
To homepage To homepage
Solved

Limiting data ingested into Dev DW Instance

P
Contributor
Forum|alt.badge.img+2

Hi,

In version 20, we have a setup with two environments, a dev and a prod, that ingests data via a business unit. We are limiting the data ingested into dev by using the “Environment name” project variable together with a date filter, much like what is described here:
https://legacysupport.timextender.com/hc/en-us/articles/360032668012-Creating-Dynamic-Data-Selection-Rules-using-Project-Variables

What is the equivalent of doing this in the latest version of TimeXtender? The client’s setup has one ODX and two DW instances (dev and prod). Their need is to limit the amount of data ingested into the Dev DW instance. Is this possible with the features available in version 6436.1?

Best,

Pontus Berglund

Best answer by rvgfox

@pontus.berglund You can create a Dynamic variable like this:

 

SELECT CASE 
    WHEN RIGHT(@@SERVERNAME,4)='-DEV'
	AND RIGHT(DB_NAME(),4)='-DEV'
	THEN 'Development'
    WHEN RIGHT(@@SERVERNAME,4)='-DEV'
	AND RIGHT(DB_NAME(),5)='-TEST'
	THEN 'Testing'
    ELSE 'Production'
END


 

View original
    Did this topic help you find an answer to your question?

    8 replies

    R
    Contributor
    • RLB
    • Contributor
    • 75 replies
    • December 19, 2023

    I think you should still be able to set up data selection rules based on instance variables or project variables? E.g. project variable Environment Name (of type System): 

     

    P
    Contributor
    Forum|alt.badge.img+2

    Hi @RLB,

    Unfortunately for instance variables, there is no “Environment Name” System type variable or equivalent that I have found. This is indeed what we use in version 20 when using project variables. 

     

    rvgfox
    Problem Solver
    Forum|alt.badge.img+4
    • rvgfox
    • Problem Solver
    • 222 replies
    • Answer
    • December 19, 2023

    @pontus.berglund You can create a Dynamic variable like this:

     

    SELECT CASE 
    WHEN RIGHT(@@SERVERNAME,4)='-DEV'
	AND RIGHT(DB_NAME(),4)='-DEV'
	THEN 'Development'
    WHEN RIGHT(@@SERVERNAME,4)='-DEV'
	AND RIGHT(DB_NAME(),5)='-TEST'
	THEN 'Testing'
    ELSE 'Production'
END


     

    P
    Contributor
    Forum|alt.badge.img+2

    Hi @rvgfox,

    Thanks, yeah we were discussing doing something like this, and I agree it’s probably the best solution as of now. It would be nice if there was a no (or low) code solution, but I’m sure that’s on its way.

    R
    Participant
    • RobertU
    • Participant
    • 25 replies
    • July 1, 2024

    @pontus.berglund  Did you ever implement a workable solution? We also want to limit the amount of records ingested in our DEV environment. Right now you can't use custom data selection rule when the data is coming from ODX Server, so the dynamic variable is not going to work on the DSA.

     

    P
    Contributor
    Forum|alt.badge.img+2

    @RobertU, we ended up creating an instance variable that we named “storage database” where we used “SELECT DB_NAME()”. We then used a data selection rule on an appropriate date field filtering on “greater than 2024-01-01” with a condition that “storage database = DB_Dev”.

    It’s not very dynamic unfortunately, but it did the trick for us.

    rory.smith
    TimeXtender Xpert
    Forum|alt.badge.img+7
    • rory.smith
    • TimeXtender Xpert
    • 652 replies
    • July 1, 2024

    Hi,

    upvoting this: 

    https://support.timextender.com/ideas/use-instance-variables-on-data-selection-rules-from-odx-server-tables-2224

    should hopefully help to get this improved in future.

    R
    Participant
    • RobertU
    • Participant
    • 25 replies
    • July 1, 2024

    @pontus.berglund Thank you for your response. Will try your solution, it is something at least. Hopefully they will come up with a proper solution in the foreseeable future.

    Reply


    Most helpful members this week

    Terms and ConditionsCookie settings

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie settings