SQL Server 2012
- The log file '{0}' already exists. Would you like to overwrite this file or append conflict information to the end of it? ...
- The log file name "%1!s!" is invalid. Verify that the file exists and that the SQL Server service account has access to it. ...
- The log file path '%ws' to the ETW target is invalid. Verify that the path exists and that the process startup account has ...
- The log for database '%1!s!' is not available. Check the event log for related error messages. Resolve any errors and restart ...
- The log in this backup set begins at LSN %1!s!, which is too recent to apply to the database. An earlier log backup that ...
- The log in this backup set begins at LSN %1!s!, which is too recent to apply to the database. This restore sequence needs ...
- The log in this backup set contains bulk-logged changes. Point-in-time recovery was inhibited. The database has been rolled ...
- The log in this backup set terminates at LSN %1!s!, which is too early to apply to the database. A more recent log backup ...
- The log provider "%1!s!" cannot log messages on the installed %2!s! of SQL Server. The log provider requires %3!s! or higher. ...
- The log provider "%1!s!" cannot log messages on the installed edition of SQL Server. The log provider requires %2!s! or higher. ...
- The log provider for SQL Server Profiler was unable to load pfclnt.dll. Please check that SQL Server Profiler is installed. ...
- The log provider type "%1!s!" specified for log provider "%2!s!" is not recognized as a valid log provider type. This error ...
- The log provider type is not recognized as a valid log provider type. This error occurs when an attempt is made to create ...
- The Log Reader Agent encountered a NULL command that is not valid. Restart the agent if it has stopped. If the problem persists, ...
- The Log Reader Agent is scanning the transaction log for commands to be replicated. Approximately %1!d! log records have ...
- The Log Reader Agent scanned to the end of the log before processing all transactions in the hash table. %1!s! transactions ...
- The Log Reader Agent scanned to the end of the log while processing a bounded update. BEGIN_UPDATE LSN {%1!s!:%2!s!:%3!s!}, ...
- The Log Reader Agent was unable to connect to the Publisher using the specified login. Make sure that the login used by the ...
- The log reader encountered a 'CANNOT SERIALIZE TRANSACTION' error (ORA-08177) while creating an XactSet at the publisher. ...
- The log reader encountered a 'SNAPSHOT TOO OLD' error (ORA-01555) while creating an XactSet at the publisher. The creation ...
- The log reader encountered an 'OBJECT NOT FOUND' error (ORA-00942) while creating an XactSet at the publisher. The creation ...
- The log scan number %1!s! passed to log scan in database '%2!s!' is not valid. This error may indicate data corruption or ...
- The log shipping primary database %1!s!.%2!s! has backup threshold of %3!s! minutes and has not performed a backup log operation ...
- The log shipping secondary database %1!s!.%2!s! has restore threshold of %3!s! minutes and is out of sync. No restore was ...
- The log was not truncated because records at the beginning of the log are pending replication or Change Data Capture. Ensure ...
- The Log-Scan Process failed to construct a replicated command from log sequence number (LSN) {%1!s!:%2!s!:%3!s!}. Back up ...
- The logging level '%1!s!' is undefined. Provide one of the following logging levels: 0 (None), 1 (Basic), 2 (Performance), ...
- The logical file cannot be found inside the physical file. Physical file: %{PhysicalFile/}. Logical file: %{LogicalFile/}. ...
- The logical primary key of the selected dimension table contains column types not supported as key columns. Clear the check ...
- The logical record relationship between articles "%1!s!" and "%2!s!" cannot be added because at least one of the articles ...
- The login '%1!s!' does not have access permission on publication '%2!s!' because it is not in the publication access list. ...
- The login attempt failed for "%1!s!". This error occurs when the login credentials provided are incorrect. Verify the login ...
- The login failed for user "%1!s!". The password change failed. An unexpected error occurred during password validation. %2!s! ...
- The login failed for user "%1!s!". The password change failed. Password change during login is not supported in this version ...
- The login failed for user "%1!s!". The password change failed. The password does not meet the requirements of the password ...
- The login failed for user "%1!s!". The password change failed. The user does not have permission to change the password. ...
- The login has insufficient authority. Membership of the sysadmin role is required to use VIRTUAL_DEVICE with BACKUP or RESTORE. ...
- The login name of the user who originated the session. For example, if you connect to SQL Server using Login1 and execute ...
- The login packet used to open the connection is structurally invalid; the connection has been closed. Please contact the ...
- The login you entered does not have the necessary permissions to save the security configuration on server instance '{0}'. ...
- The login you specified when connecting to server instance '{0}' has limited permissions for monitoring database mirroring. ...
- The Lookup output that handles rows with no matching entries in the reference dataset. Use this output when the NoMatchBehavior ...
- The Lookup output that handles rows with no matching entries in the reference dataset. Use this output when the NoMatchBehavior ...
- The lookup transform must contain at least one input column joined to a reference column, and none were specified. You must ...
- The Lookup transformation failed to retrieve any rows. The transform fails when the FailOnLookupFailure is set to TRUE and ...
- The Lookup transformation reference metadata contains too few columns. Check the SQLCommand property. The SELECT statement ...
- The machine is clustered, but the cluster is not online or cannot be accessed from one of its nodes. To continue determine ...
- The magnitude of the result of a function call was too big to fit in the result type, and overflowed the type of the operand. ...
- The main assembly has the same public key as the components installed by SQL Server Setup, you cannot use it as the main ...
- The main assembly has the same public key as the components installed by SQL Server Setup. You cannot use it as the main ...
- The Management Data Warehouse version "%s" is not supported by the current data collector. Please upgrade the Management ...
- The Management Data Warehouse version is incompatible with the current reports. Please contact the administrator for the ...
- The Management Portal for SQL Azure cannot connect to server {0}'. To continue, use the Windows Azure Portal to update the ...
- The Many-to-many and Many-to-one conversion options are not valid because a single currency has been selected as the base ...
- The map, {0}, was detected in the report. SQL Server 2008 Reporting Services does not support map report items. Either reduce ...
- The mapping for column '%1' of article '%2', publication '%3' is not suitable for parameterized commands. Change the mapping ...
- The marked transaction "%1!s!" failed. A timeout occurred while attempting to place a mark in the log by committing the marked ...
- The master merge started at the end of the full crawl of table or indexed view '%1!s!' failed with HRESULT = ' 2!s!'. Database ...
- The master server operator will be created on the master server and each of the target servers. Multiserver jobs can only ...
- The matching configuration has been changed by another user, Your changes cannot be saved. The new settings are about to ...
- The matrix {1}' contains a different number of MatrixColumn elements than the number of StaticColumn elements. If the matrix ...
- The matrix {1}' contains a different number of MatrixRow elements than the number of StaticRow elements. If the matrix contains ...
- The matrix {1}' has a MatrixRow that contains a different number of MatrixCell elements than the number of StaticColumn elements ...
- The maximum allow integer identity value has been reached. Consider re-building the error tolerant index to use any gaps ...
- The maximum amount of time, in minutes, that Database Engine Tuning Advisor will spend tuning. In general, longer times produce ...
- The Maximum insert commit size property of the OLE DB destination "%1!s!" is set to 0. This property setting can cause the ...
- The Maximum insert commit size property of the OLE DB destination "{0}" is set to 0. This property setting can cause the ...
- The maximum number of days that a stored parameter can be stored. Valid values are 1 through 2,147,483,647. The default value ...
- The maximum number of snapshots that are stored for a report. Valid values are -1 and 1 through 2,147,483,647. If the value ...
- The maximum system-generated unique value for a duplicate group was exceeded for index with partition ID %1!s!. Dropping ...
- The maximum time, in seconds, that the principal server instance waits for a PING message from another instance in the mirroring ...
- The MAXIMUM_BUCKETS_FOR_CONTINUOUS_SPLIT parameter for the '%{modelname/}' model is not valid. MAXIMUM_BUCKETS_FOR_CONTINUOUS_SPLIT ...
- The MAXIMUM_CLUSTER_COUNT parameter is negative in the '%{modelname/}' Microsoft Sequence Clustering model. MAXIMUM_CLUSTER_COUNT ...
- The MAXIMUM_CONTINUOUS_INPUT_ATTRIBUTES parameter for the %{modelname/} model is not valid. MAXIMUM_CONTINUOUS_INPUT_ATTRIBUTES ...
- The MAXIMUM_INPUT_ATTRIBUTES parameter for the %{modelname/} model is not valid. MAXIMUM_INPUT_ATTRIBUTES must be at least ...