Agents
Support Requested My Configuration Database
Answered
Yellowfin Support has requested a backup of my Yellowfin Configuration Database to replicate an issue I'm facing. Doesn't this contain private data?
The same question
In regards to the Configuration Database, by default this will not contain any of your report data and is generally safe to share. Below are the considerations if concerned about transferring the requested component:
User Accounts - names and email addresses in the 'IpClass', 'Person', and 'IpContact' tables. These can be scrubbed or removed. Please retain the record WHERE IpId = 5.
Cached Filter Values - these are stored in the database in the 'CachedFilterValue' table. This can be safely truncated.
Cached Report Sets (if enabled) - these are byte encoded and stored as a chunk in the 'DocumentData' table. In the event you wish to remove these before submission, you can review this post for some direction.
Database Connection Info - Passwords here are encrypted, salted, and hashed. 'UserName' and 'DatabaseURL' can be obfuscated if desired.
Signals - If you have Analytics Plus or a Signals package, the 'SignalSearchTexts' table may contain clues as to the data being analyzed. Obfuscating the 'SearchableWords' field will mitigate this.
Thanks,
Ryan
In regards to the Configuration Database, by default this will not contain any of your report data and is generally safe to share. Below are the considerations if concerned about transferring the requested component:
User Accounts - names and email addresses in the 'IpClass', 'Person', and 'IpContact' tables. These can be scrubbed or removed. Please retain the record WHERE IpId = 5.
Cached Filter Values - these are stored in the database in the 'CachedFilterValue' table. This can be safely truncated.
Cached Report Sets (if enabled) - these are byte encoded and stored as a chunk in the 'DocumentData' table. In the event you wish to remove these before submission, you can review this post for some direction.
Database Connection Info - Passwords here are encrypted, salted, and hashed. 'UserName' and 'DatabaseURL' can be obfuscated if desired.
Signals - If you have Analytics Plus or a Signals package, the 'SignalSearchTexts' table may contain clues as to the data being analyzed. Obfuscating the 'SearchableWords' field will mitigate this.
Thanks,
Ryan
In regards to the Configuration Database, by default this will not contain any of your report data and is generally safe to share. Below are the considerations if concerned about transferring the requested component:
User Accounts - names and email addresses in the 'IpClass', 'Person', and 'IpContact' tables. These can be scrubbed or removed. Please retain the record WHERE IpId = 5.
Cached Filter Values - these are stored in the database in the 'CachedFilterValue' table. This can be safely truncated.
Cached Report Sets (if enabled) - these are byte encoded and stored as a chunk in the 'DocumentData' table. In the event you wish to remove these before submission, you can review this post for some direction.
Database Connection Info - Passwords here are encrypted, salted, and hashed. 'UserName' and 'DatabaseURL' can be obfuscated if desired.
Signals - If you have Analytics Plus or a Signals package, the 'SignalSearchTexts' table may contain clues as to the data being analyzed. Obfuscating the 'SearchableWords' field will mitigate this.
Thanks,
Ryan
In regards to the Configuration Database, by default this will not contain any of your report data and is generally safe to share. Below are the considerations if concerned about transferring the requested component:
User Accounts - names and email addresses in the 'IpClass', 'Person', and 'IpContact' tables. These can be scrubbed or removed. Please retain the record WHERE IpId = 5.
Cached Filter Values - these are stored in the database in the 'CachedFilterValue' table. This can be safely truncated.
Cached Report Sets (if enabled) - these are byte encoded and stored as a chunk in the 'DocumentData' table. In the event you wish to remove these before submission, you can review this post for some direction.
Database Connection Info - Passwords here are encrypted, salted, and hashed. 'UserName' and 'DatabaseURL' can be obfuscated if desired.
Signals - If you have Analytics Plus or a Signals package, the 'SignalSearchTexts' table may contain clues as to the data being analyzed. Obfuscating the 'SearchableWords' field will mitigate this.
Thanks,
Ryan
Replies have been locked on this page!