Envision: Why are we writing to the master database when collecting Microsoft SQL database logs
Originally Published: 2008-06-17
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 My Page SSO Configuration - RSA Ready Implementation Guide Number of Views Way We Do - SAML Relying Party 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 Error message "Our process does not support use of public accounts" when registering for an RSA Community or myRSA account Number of Views
Trending Articles
RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows RSA Authentication Manager Upgrade Process How to Update the Root (Server) and Client Certificates in RSA Identity Governance & Lifecycle RSA Release Notes: Cloud Access Service and RSA Authenticators RSA Authenticator 6.2.2 for Windows Administrator Guide
Don't see what you're looking for?
