A database index is a data structure that improves the speed of operations in a table. Indices can be created using one or more columns, providing the basis for both rapid random lookups and efficient ordering of access to records. The disk space required to store the index is typically less than the storage of the table (since indices usually contain only the key-fields according to which the table is to be arranged, and excludes all the other details in the table), yielding the possibility to store indices into memory from tables that would not fit into it. In a relational databasean index is a copy of part of a table. Some databases extend the power of indexing by allowing indices to be created on functions or expressions. For example, an index could be created on upper(last_name), which would only store the uppercase versions of the last_name field in the index. Another option sometimes supported is the use of "filtered" indices, where index entries are created only for those records that satisfy some conditional expression. A further aspect of flexibility is to permit indexing on user-defined functions, as well as expressions formed from an assortment of built-in functions.

Windows SharePoint Services can use any of the following three options from ASP.NET and the
CLR to provide assemblies installed in the BIN directory with sufficient permissions. The
following table outlines the implications and requirements for each option.
Option Pros Cons Increase the trust level for the entire virtual server.

The parameters to your script can be passed as -n 15 -x 20. Inside the script, you can iterate through the getopts array as while getopts n:x option, and the variable $option contains the value of the entered option.

The recovery model is a database property. It defines the method you wish to use when recovering your database; depending on the mode you select, different amounts of information will be preserved for each backup. Simple recovery: This option restores a database to its state at the time of its most recent backup. Any changes made after the last full or differential backup are lost (no transaction log backups are made). Full recovery: This option restores a database to its state at the point of failure. Bulk-logged recovery: This option enables bulk-logged operations, which means that certain database operations, such as SELECT INTO operations or BCP/Bulk Copy, will be logged minimally or not at all. The risk of data loss is higher than with the full-recovery model, as bulk-logged recovery does not provide point-in-time recovery

You can create a Windows NT ERD using the Repair Disk program (RDISK.EXE). To do so, select the Run option from the Start menu, enter the CMD command in the Run dialog box, and then type RDISK at the command prompt.

If the Normal option is selected, the system tries to restart as it would normally, loading all of its normal startup and Registry files. The Logged also attempts to start the system in normal mode, but keeps an error log file that contains the steps performed and outcome. This text file (BOOTLOG.TXT) can be read with any text editor or printed out on a working system.