This blog post is about SafePeak “Logon Trigger” Feature for Managing Data Access. Just a quick update the product is no longer available.
Counting Users, Roles and Orphans in Every Database
Audit counting users across databases, include roles and schema ownership, and distinguish orphaned SQL users from contained identities.
Contained Database Users: Logins That Move With the Database
Use contained database users to move authentication with a database, inspect prerequisites, test connections, and review access ownership.
Giving Web Developers Safe Database Access
Give web developers safe database access with narrow roles and views, a reporting replica where useful, and audit that identifies real changes.
Finding Unused Logins and Users Before an Audit
Review unused logins with password metadata, database mappings and activity capture, then use an owner approved disable-first plan.
SQL SERVER – FIX : ERROR : Cannot open database requested by the login. The login failed. Login failed for user ‘NT AUTHORITY\NETWORK SERVICE’.
Getting Cannot open database requested by the login for NT AUTHORITY\NETWORK SERVICE? Map that login to your database under User Mapping.
Hunting Suspicious Objects After a SQL Server Compromise
Investigate a SQL Server compromise by preserving evidence and checking logins, startup procedures, Agent jobs, risky features, and changed objects.