Recording the Database Name in the Auxiliary Log Database

Translated post:

Currently, the TARGIT Auxiliary Log Database records only the cube name. For DAX/Tabular models, the cube name is typically "Model," making it impossible to identify which database is actually being used. We currently have five cubes named Model.

I therefore propose that the database name be recorded as a separate field in the Auxiliary Log Database alongside the existing log information.

This would make it possible to analyze database usage over time and identify which databases are used most frequently. This information is partially available in TARGIT Insights, but its historical data is limited, making the Auxiliary Log Database the preferred source for longer-term analysis.

Expected benefits:

• Unambiguous identification of the database being used.
• Better analysis of user behavior and database usage.
• Ability to perform historical reporting over longer periods.
• More valuable log data in environments with multiple DAX/Tabular databases.

 

Original Danish post:

Registrering af databasenavn i Auxiliary Log Database

I TARGIT Auxiliary Log Database registreres i dag kun kubenavnet. For DAX/Tabular-modeller er kubenavnet typisk "Model", hvilket gør det umuligt at identificere, hvilken database der faktisk anvendes. Vi har pt. 5 kuber med Model

Jeg foreslår derfor, at databasenavn registreres som et separat felt i Auxiliary Log Database sammen med de eksisterende log oplysninger.

Dette vil gøre det muligt at analysere databaseanvendelse over tid og identificere, hvilke databaser der benyttes mest. Oplysningen findes delvist i TARGIT Insights, men historikken her er begrænset, hvorfor Auxiliary Log Database er den foretrukne kilde til længerevarende analyser.

Forventet gevinst:

• Entydig identifikation af anvendt database.
• Bedre analyser af brugeradfærd og databaseanvendelse.
• Mulighed for historisk rapportering over længere perioder.
• Mere værdifulde logdata i miljøer med flere DAX/Tabular-databaser.