To homepage To homepage
Solved

Limiting data ingested into Dev DW Instance

  • 18 December 2023
  • 4 replies
  • 45 views
P
Rank
Userlevel 3
Badge +1

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

icon

Best answer by rvgfox 19 December 2023, 13:13

View original

4 replies

R
Rank
Userlevel 2

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
Rank
Userlevel 3
Badge +1

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
Rank
Userlevel 3
Badge +1

@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
Rank
Userlevel 3
Badge +1

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.

Reply


Terms and ConditionsCookie settings