Archive for June 2011

Freedom Day SALE By uCertify…

Come on friends uCertify is again ready to give you special gifts in the month of July by announcing the annual Freedom Sale!
Choose from over 300 exams, covering all major certification vendors. Second, if, for any reason you are not satisfied with your purchase, simply let us know within 7 days of your order, and we will return your money. How cool is that?! This super guarantee is in addition to our unbeatable 1 year guarantee.

So, what are you waiting for? Hurry! The Freedom offer is valid June 29 – July 6, 2011 only.

Happy Shopping & Happy Learning!
Your uCertify Team

http://www.ucertify.com

Share

Privileges of Database Administrator revoked by Oracle Database Vault

The following privileges of Database Administrator are revoked by Oracle Database Vault:
BECOME USER
SELECT ANY TRANSACTION
CREATE ANY JOB
CREATE EXTERNAL JOB
EXECUTE ANY PROGRAM
EXECUTE ANY CLASS
MANAGE SCHEDULER
DEQUEUE ANY QUEUE
ENQUEUE ANY QUEUE
MANAGE ANY QUEUE

Share

The SYSASM privilege

The SYSASM privilege is created in Oracle Database 11g to further facilitate separation of duties within the Oracle environment. Using the SYSASM privilege for ASM administration creates a clearer division of responsibility between ASM administration and database administration. An optional capability is also provided to prevent different databases using the same storage from accidentally overwriting each others files. As with the SYSDBA privilege, one can create a user with the SYSASM privilege for an ASM instance. However, since there is no data dictionary in an ASM instance, the credentials are only stored in the password file. Otherwise, operating system credentials can be used to connect to the ASM instance. The SYSDBA privilege is still available for use in an ASM instance, but is deprecated; a message is written to the ASM instance’s alert log. Using SYSDBA in an ASM instance will be removed in a future release. Note: SYSDBA is for general database and instance maintenance operations, SYSOPER is for startup/shutdown and other restricted tasks, and SYSASM is to specifically manage an ASM instance.

Share

The db_dtsltduser fixed-database role

The db_dtsltduser fixed-database role secures the SSIS packages that are stored in the MSDB database. The members of the db_dtsltduser fixed database role have the following permissions:
A user can enumerate all packages.
A user can view packages owned by him.
A user can execute packages owned by him.
A user can export packages owned by him.
A user can import all packages.
A user can delete packages owned by him.
A user can change the roles of the packages owned by him.

Share

The db_dtsadmin fixed database role

The db_dtsadmin fixed database role secures the SSIS packages that are stored in the MSDB database. The members of the db_dtsadmin fixed database role have the following permissions:
Enumerate all packages.
View all packages.
Execute all packages including the packages in the SQL Server Agent.
Export all packages.
Import packages.
Delete all packages.
Change the package roles.

Share

db_securityadmin role

The members of the db_securityadmin role are allowed to manage database users. They can grant, deny, or revoke permissions from the users. The permissions include adding or removing users from a database and assigning a user to a database-level role. The members of this role can also manage statement and object permissions.

Share

db_owner database role

The db_owner database role makes its members the owner of the database. The members can perform any task such as deleting database objects, monitoring the database, executing system stored procedures against the database, etc. A member should be assigned to a database role only when he has to completely control the database.

Share

custom database role

A custom database role is mainly created to assign different permissions on the database to users according to their needs. Some users may need both Execute and Update permissions; others may need only Execute permission and nothing more. Because none of the fixed database roles give that freedom to assign the permission to users according to their needs, the custom database role was created in SQL Server. When this database role is created, the required database permissions are assigned to this role and then users are assigned to it. A custom database role is different from a fixed database role where there is no need to assign permissions, but only users are added.

Share

Custom database role

A custom database role is mainly created to assign different permissions on the database to users according to their needs. Some users may need both Execute and Update permissions; others may need only Execute permission and nothing more. Because none of the fixed database roles give that freedom to assign the permission to users according to their needs, the custom database role was created in SQL Server. When this database role is created, the required database permissions are assigned to this role and then users are assigned to it. A custom database role is different from a fixed database role where there is no need to assign permissions, but only users are added.

Share

sys.dm_db_index_usage_stats dynamic management view

The sys.dm_db_index_usage_stats dynamic management view is used to display information regarding the counts of different types of index operations and the time each type of operation was last performed. Whenever any individual uses the seek, scan, lookup, or update command on the specified index by a query execution, it is counted as a use of that index and the corresponding counter gets incremented in this view.

Share