working with multiple project

  • 14 January 2020
  • 3 replies

Hi , 

our DH setup consists of multi-layered datawarehouse whereas BI client (tableau ) only interfaces the upper tier: MDW DWH.

Having semantic layer for each dashboards (we have quite a few), we would like to move out of the single core TX project with multiple semantic layers to a project for each dashboard (semantic layer). 

By doing so, we can make sure that each developer works on his own project without "stepping on each other toes" (I'm aware of collabaration features of TX) and keeping our core project unharmed. 

So, the challenge is how to reuse objects created in the core project (preferably VIEW to reduce space/redundencies) in entire new project (same server/database)

My approach was creating a new project, add MDW datawarehouse and then utilize External SQL Connection to connect to the same DWH (transfer type connection). I've also created a seperate database schema with valid behaivor. 

The problem we ran in was that designated table was the same as similar table in the daatabae. error was occurred


My questions: 

1) Is there a smarter way (probably!) to reuse objects in projects?

2) Is it actually good practice? or should i go back to one project containing all 


Love to hear your take one it


With kind regards, 




Best answer by JTreadwell 15 January 2020, 02:30

View original

3 replies

Userlevel 3
Badge +5

Hi Dror, Thanks for posting.

While I wouldn't typically recommend this approach, you seem to be pretty confident this is what you want. 

The issue you are facing here is in your "Schema" setup. 

You need to change the schema behavior to "Default", this will move ALL objects, including any stored procedures or raw tables into this new schema. 

If the schema behavior is set to "Valid" only the valid tables are moved to this new schema. Hope that helps. 

Hi Joseph,

Thank you for your helpful reply. I actually figured this out but forgot to mention it here.

What would be, in your eyes, the right approach for collaboratively working on the sae DWH? team development witb object locking?

Note that we only have PRD environment

I would love to hear your thoughts,


Love to hear your thoughts

Userlevel 3
Badge +5

Yes, personally I would recommend team development with a close eye on work items and save+reload often. With your approach you lose data lineage, documentation, and managed execution & monitoring across your projects. That being said, your approach would be the next best choice.