This secondary database is not functional because the required copy or restore job cannot be found. You must remove this secondary database by clicking Remove. To resume log shipping to this secondary database, add it as a secondary again using the same settings. If you resume log shipping and you specify the same restore path that you used before, any backup files that are uncopied or unrestored to this database will be copied and restored when it is added as a secondary again. Reinitializing the secondary database is unnecessary.
This row has been deleted. If you choose to ignore the conflict, Microsoft SQL Server will try to reinsert the deleted row, ...
This row was successfully committed to the database. However, a problem occurred when attempting to retrieve the data back ...
This schedule requires an end date. Please specify the date at which this schedule expires, or clear the end date check box ...
This script was imported through the linked object wizard //by {0} on {1}. //Some of its calculations may not apply if they ...
This secondary database is not functional because the required copy or restore job cannot be found. You must remove this ...
This selection creates a new column when you generate the schema. If you select this option, you must run the Schema Generation ...
This server does not have one or more of the database objects required to use database diagramming. Do you wish to create ...
This server instance is acting as a Log Shipping monitor for Instance {0}, database {1}, which is configured as a Log Shipping ...
This server instance is not running SQL Server 2005 SP1 or later, so some information about database mirroring is unavailable. ...