Computer Associates SQLSTQ99000600 Microsoft SQL Guide - Page 52

Database Consistency Check (DBCC) Options, After restore

Get Computer Associates SQLSTQ99000600 - Unicenter SQL-Station 6.0.0 PDF manuals and user guides
UPC - 757943257441
View all Computer Associates SQLSTQ99000600 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 52 highlights

Restore Options Leave database nonoperational, but able to restore additional transaction logs Instructs the restore operation not to roll back any uncommitted transactions and to leave the database in a state where it can accept additional Files-and-FileGroups, Differential, or Transaction Log restores. You must choose either this option or the Leave database read-only option to apply another differential backup or Transaction log after this restore job is complete. This option is generally used when restoring a database from multiple sessions without using Automatic Selection. Leave database read-only and able to restore additional transaction logs Prepares a standby (warm backup) database. A standby database is a second database on a different server which you can bring online if the primary production server fails. It contains a copy of the database on the primary server. The database is brought online in a special form of Read-Only state which can be revered to a Restoring state if another restore occurs. An Undo File is created during the restore which contains the information SQL Server needs to make this transition. The location and filename of the Undo File must be specified in the restore options. Note: Standby databases are not eligible for backup. If a standby database is explicitly selected for backup, the backup will fail. If a SQL Server instance which contains a standby database is selected for backup, the standby database will be excluded by the agent. For more information about standby servers, see Microsoft SQL Server documentation. Database Consistency Check (DBCC) Options A database consistency check (DBCC) tests the physical and logical consistency of a database. DBCC provides the following options: After restore Performs DBCC after the restore of the database. Before restore Performs DBCC before an Online Torn Page Repair restore of the database. (SQL Server 2005 or later, Enterprise Edition only.) Do not check indexes Checks the database for consistency without checking indexes for user-defined tables. Note: The system table indexes are checked regardless of whether you select this option. 52 Agent for Microsoft SQL Server Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
Restore Options
52
Agent for Microsoft SQL Server Guide
Leave database nonoperational, but able to restore additional
transaction logs
Instructs the restore operation
not
to roll back any uncommitted
transactions and to leave the database in a state where it can accept
additional Files-and-FileGroups, Differential, or Transaction Log restores.
You must choose either this option or the Leave database read-only option to
apply another differential backup or Transaction log after this restore job is
complete. This option is generally used when restoring a database from
multiple sessions without using Automatic Selection.
Leave database read-only and able to restore additional transaction
logs
Prepares a standby (warm backup) database. A standby database is a
second database on a different server which you can bring online if the
primary production server fails. It contains a copy of the database on the
primary server. The database is brought online in a special form of
Read-Only state which can be revered to a Restoring state if another restore
occurs. An Undo File is created during the restore which contains the
information SQL Server needs to make this transition. The location and
filename of the Undo File must be specified in the restore options.
Note:
Standby databases are not eligible for backup. If a standby database
is explicitly selected for backup, the backup will fail.
If a SQL Server instance
which contains a standby database is selected for backup, the standby
database will be excluded by the agent.
For more information about standby servers, see Microsoft SQL Server
documentation.
Database Consistency Check (DBCC) Options
A database consistency check (DBCC) tests the physical and logical consistency
of a database. DBCC provides the following options:
After restore
Performs DBCC after the restore of the database.
Before restore
Performs DBCC before an Online Torn Page Repair restore of the database.
(SQL Server 2005 or later, Enterprise Edition only.)
Do not check indexes
Checks the database for consistency without checking indexes for
user-defined tables.
Note:
The system table indexes are checked regardless of whether you
select this option.