Implementing New Manageability Features and Practices - Microsoft SQL Server 2008 R2 Administration - page 273

How it works...
The security context is managed by precedence (nested hierarchy of securable permissions)—
permissions denied at a higher scope in the security model override grants on that permission
at a lower scope. GRANT permission removes DENY or REVOKE of that permission on the
specified securable. If the same permission is denied at a higher scope that contains the
securable, the DENY takes precedence. But revoking the granted permission at a higher scope
does not take precedence.
Database-level permissions are granted within the scope of the specified database. If a user
needs permissions to objects in another database, then they will need to create the user
account in the other database, or grant the user account access to the other database, as
well as the current database. When allocating permissions on a securable to a principal, the
person doing the allocation is the Grantor, and the principal receiving the permission is the
Grantee.
To explicitly deny permissions on a securable to a server-level principal, use the DENY
command. To revoke permissions on a securable to a principal, use the REVOKE command.
Revoking a permission means you are neither granting nor denying permission. Revoking
removes the specified permission(s) that had previously been either granted or denied.
The Has_perms_by_name system function evaluates whether or not the current connection
has granted permissions to access a specific securable (granted permissions either explicitly
or inherently through a higher scoped securable).
Implementing backup compression for a
VLDB environment
VLDB (Very Large Databases ) have a specific requirement in terms of storage. The time
required to backup increases, the method of backup is changed compared to normal
databases and the recovery process is only a partial recovery process. Since SQL Server
2008, native backup compression was introduced for the Enterprise edition and SQL Server
2008 R2 has extended the feature to the Standard and Datacenter editions, for production
purposes. The functionality allows the backup process to consume less disk space. The
amount of compression gained depends on the data within the database. From the SQL
Server 2008 Service Pack 2 onwards, every edition of SQL Server 2008 version and higher
versions can restore a compressed backup.
Filegroups are often used for very large databases for the ease of backup administration and
to improve performance by distributing data files over disk LUNs. In order to provide a quicker
recovery process for a VLDB environment, backup compression must be considered. In this
recipe, we will go through the important steps in implementing backup compression for the
VLDB environment.