SQL Server organizes the transaction log as reusable virtual log files. However, there are eight reasons that can prevent their reuse causing the log file to grow. Find out what those reasons are and what to do about it.
The SQL Server functions SUSER_NAME() and SUSER_SNAME() both return the current login name. So why are there two? Read on to find out what the difference is.
Worried about unauthorized REVERTing after using EXECUTE AS? Read on to get all the details about EXECUTE AS WITH NO REVERT and EXECUTE AS WITH COOKIE.
Constantly logging out and back in to test security settings and permissions can be cumbersome. Learn how EXECUTE AS can ease your life.
To determine the active permissions for a connection, SQL Server uses a list of security tokens. Read on to find out what these mysterious tokens are and how to see the list of active ones.
Database roles can greatly simplify permission management on a database level. Learn how to add and remove members and how to retrieve the list of all current members of a database role.
Database roles simplify security management on a database level. With database roles we can grant or deny permissions to a group of database users. Find out how you can use database roles in your environment.
Server Roles allow for simplified security management for server level permissions in SQL Server. Learn how to add new members, remove existing ones or list all current members of a server role. [more…]
Server roles simplify management of server level permissions. Before SQL Server 2012 we were confined to 9 fixed server roles. However, now we are able to create user-defined server roles and grant any server level permission to them. Read on to find out more…
Database principals like the database user allow use to grant permissions on objects in a given database. Check out how to list users and find their linked logins.