Solved

Working with multiple environments


I would like to know what the best way of working is if you have multiple environments (DEV, TST, PRD) with the new version. In the old version you had to open a different project repository that you could set a different color, so you were always aware on what you had open.

In the new version all the environments are available in the desktop and a mistake is very easily made on what environment you open. Names are also shared between environments so you never know what DSA you have open.

Love to hear some comments on how other customers are working.

 

icon

Best answer by rory.smith 1 July 2024, 13:25

View original

5 replies

Userlevel 6
Badge +7

Hi,

in the new release your application settings are separate from the environment indeed. As you can also open multiple DWH and SSL instances at once, you need to keep track of the selected column's associated instance name in the Title bar. So there is a visual way to know, but it is somewhat subtle.

I tend to avoid setting up services for multiple environments on one VM as much as possible (to avoid Dev resource use blocking Prod performance for instance) and colour window accents in Windows according to the environment the VM belongs to. This means I also don't get confused as easily when doing software installs etc. This does mean keeping to the “open only one instance per VM session" rule manually.

 

 

@rory.smith I think i am missing something. I have created 3 environments each with a datawarehouse instance in them and also some semantic models. When i log in to Timextender Desktop it automatically shows all 3 the environent. 

As i understand correctly from your post there is a way to avoid this and only show one environment per VM?

Userlevel 6
Badge +7

Hi,

no you aren't missing anything - you always see all instances, but you should only open the instance matching your machine and only have one instance per environment open. There is no way to handle this in the software other than to create separate logins per environment, but that is too much hassle in my opinion.

Userlevel 6
Badge +5

Hi @RobertU 

I think the only way to limit what you can see is if you set up a specific user account in the portal without any admin rights and then apply it to either the dev, test or prod instances.

So here I got my low access account.

I applied it as an user to all instances called DEV something.

Here is what I saw when I logged in.

 

This is normally looks when I log in with my main account.

 

Userlevel 6
Badge +5

@RobertU please feel free to submit a product idea here for suggested improvements to multiple environments 

Reply