The log copier for database '%1' detected that the end of log is changing from generation %2 to %3. This passive copy will reinitialize to ensure that a log stream reset is handled correctly.
The location of one or more transaction log files may be contributing to a performance bottleneck. This may not be an issue ...
The location of the page file, SMTP server, TEMP or TMP directory may contribute to a performance bottleneck. If there is ...
The location that you specified for the transaction log files is invalid. Verify that the directory exists and that there ...
The log copier couldn't continue processing because a gap in the log sequence has been detected. Source server '{0}' doesn't ...
The log copier for database '%1' detected that the end of log is changing from generation %2 to %3. This passive copy will ...
The log copier for database '%1' detected that the end of log is changing from generation %2 to %3. This passive copy will ...
The log copier for database '%1' has been disconnected for '%2'. This has exceeded the configured limit and the copy is being ...
The log copier for database '%1' has been disconnected for '%2'. This has exceeded the configured limit and the copy is being ...
The log copier for database '%1' received an error from the source server '%2': %3 The copier will automatically retry after ...