Environment name variable in new TimeXtender

Great Idea, Really missing this functionality!

Hi,

The instance name might be easier to implement as an instance variable in a prepare instance.
In the same way that you can now use endpoint names for filtering with variables in a deliverer instance.
It would really be good if it was possible to filter tables in, for example, the prepare instances for development and testing only.

Hi,

while you can currently almost approach this with the machine name system variable in prepare instances, I think there should be a whole set of system variables so you can find out from a bit of custom SQL where it is being run:

• Database metadata:
  • Field name
  • Table / View name, i.e. table_R for a raw table
  • Schema
• TDI metadata:
  • Table / View metadata:
    • name, i.e. the name in the TDI interface
    • Table cleanse procedure name
    • Table transformation view name
  • Data Area name
  • Database name
  • SQL Instance
• Portal metadata:
  • Instance type
  • Instance name
  • Instance infrastructure type (Azure SQL DB, Snowflake, etc)
  • Instance infrastructure name, i.e. the hostname of the infrastructure
  • Instance version, i.e. the TIS / TDI version attached to the metadata of the instance
• Execution metadata:
  • machine name
  • username
  • domainname
  • UPN of user under Entra context
• Environment metadata
  • Environment name

In every place you run SQL / code there should be a context like ‘this’ in object-oriented programming. It would be great to be able to query relevant system-metadata from this context. I am sure there are many more, but this should be a good place to start.