Envision: Why are we writing to the master database when collecting Microsoft SQL database logs
Originally Published: 2008-06-17
Last Modified: 2023-09-25
Article Number
Applies To
Windows
Issue
You observed that the collection process involves writing to the master database in the Microsoft SQL database. You wish to know why is that so
Resolution
Some of the reasons are:
1. master database is guaranteed to exist, not going to ask customer to create a separate database
2. one of the stored procedures requires sp_procoption and must be part of the master database to use it
Related Articles
Way We Do - SAML Relying Party Configuration - RSA Ready Implementation Guide Number of Views Way We Do - SAML My Page SSO Configuration - RSA Ready Implementation Guide Number of Views Way We Do - RSA Ready Implementation Guide Number of Views In RSA Identity Governance & Lifecycle While attempting to create/modify review definition, when we include users with Dat… Number of Views Where in enVision can we see which row was the last to be retrieved by the DB? Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.1 Quick Setup Fails with "Failed to Attach Replica Instance" User Application Portal The RSA Identity Governance & Lifecycle AD Collector and AD ADC authentication source fail to establish a TLS 1.2 SSL conn…
Don't see what you're looking for?
