Computer Associates SQLSTQ99000600 Microsoft SQL Guide - Page 53

Force Restore to use Named Pipes, Continue Restore After Checksum Failure, Miscellaneous

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 53 highlights

Restore Options Check only the physical consistency of the database Detects torn pages and common hardware failures, but does not check the data against the rules of the database schema. It still checks the integrity of the physical structure of the page and record headers, and the consistency between the page's object ID and index ID. This option is available for Microsoft SQL Server 2000 or later. If this option is selected from the Global Agent Options tab, it is ignored for SQL Server 7.0 databases. All error messages that are generated during the DBCC are recorded in the Agent for Microsoft SQL Server log file called sqlpagw.log. The log is located in the Backup Agent directory. Force Restore to use Named Pipes This option forces the agent to use Named Pipes to return the data to the Microsoft SQL Server. This provides an alternate mechanism for restoring a session if the Virtual Device Interface is not functioning properly. This option is available for Microsoft SQL Server 7.0 and Microsoft SQL Server 2000. Continue Restore After Checksum Failure This option allows Microsoft SQL Server 2005 to continue processing a restore if it detects an inconsistency between the data and checksums included in the backup. Miscellaneous The following are the miscellaneous options you can select from: Force Restore Over Existing Files and Databases Lets Microsoft SQL Server overwrite files it does not recognize as part of the database it is restoring. Use this option only if you receive a message from Microsoft SQL Server prompting you to use the With Replace option. Microsoft SQL Server supports this option for database restore and file or FileGroup restore operations. Important! Microsoft SQL Server 2005 will refuse by default to overwrite an online database using the Full or Bulk-Logged Recovery Model. Instead, it produces an error message saying to either take the database offline by performing a Log Tail backup, or restore with the "WITH REPLACE" option. Selecting this option applies the "WITH REPLACE" option to the restore, and forces SQL Server to overwrite the existing database. Chapter 4: Restoring Microsoft SQL Server Databases 53

  • 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
Chapter 4: Restoring Microsoft SQL Server Databases
53
Check only the physical consistency of the database
Detects torn pages and common hardware failures, but does not check the
data against the rules of the database schema. It still checks the integrity of
the physical structure of the page and record headers, and the consistency
between the page’s object ID and index ID. This option is available for
Microsoft SQL Server 2000 or later. If this option is selected from the Global
Agent Options tab, it is ignored for SQL Server 7.0 databases.
All error messages that are generated during the DBCC are recorded in the Agent
for Microsoft SQL Server log file called sqlpagw.log. The log is located in the
Backup Agent directory.
Force Restore to use Named Pipes
This option forces the agent to use Named Pipes to return the data to the
Microsoft SQL Server. This provides an alternate mechanism for restoring a
session if the Virtual Device Interface is not functioning properly. This option is
available for Microsoft SQL Server 7.0 and Microsoft SQL Server 2000.
Continue Restore After Checksum Failure
This option allows Microsoft SQL Server 2005 to continue processing a restore if
it detects an inconsistency between the data and checksums included in the
backup.
Miscellaneous
The following are the miscellaneous options you can select from:
Force Restore Over Existing Files and Databases
Lets Microsoft SQL Server overwrite files it does not recognize as part of the
database it is restoring. Use this option only if you receive a message from
Microsoft SQL Server prompting you to use the With Replace option.
Microsoft SQL Server supports this option for database restore and file or
FileGroup restore operations.
Important!
Microsoft SQL Server 2005 will refuse by default to overwrite an
online database using the Full or Bulk-Logged Recovery Model. Instead, it
produces an error message saying to either take the database offline by
performing a Log Tail backup, or restore with the “WITH REPLACE” option.
Selecting this option applies the “WITH REPLACE” option to the restore, and
forces SQL Server to overwrite the existing database.