SQL Server 2016
- The data for table-valued parameter "%1!s!" doesn't conform to the table type of the parameter. SQL Server error is: %2!s!, ...
- The data for the table-valued parameter %1!s! doesn't conform to the table type of the parameter. SQL Server error is: %2!s!, ...
- The data in row {0} was not committed. Error Source: {1}. Error Message: {2} Correct the errors and retry or press ESC to ...
- The data in the column '{0}' does not have the required content type. In a mining structure that has a Key Time column, any ...
- The data in the data file does not conform to the UNIQUE hint specified for the BULK rowset '%1!s!'. The data in the data ...
- The Data Mining Extensions (DMX) OPENROWSET statement supports ad hoc queries using external providers. Enable ad hoc data ...
- The data mining relationship cannot be defined because the designer failed to identify the source dimension for mining model. ...
- The data mining relationship cannot be defined because the {0} case dimension is absent in this cube and needs to be added. ...
- The Data Mining Training transformation requires at least one input. Connect an output from a source or another transformation ...
- The data model cannot be loaded because an error occurred while attempting to query the field '%{fieldname/}' in the DBPROPERTIES ...
- The data model cannot be loaded because of an inconsistency in the metadata schema versions. The last known schema version ...
- The data model cannot be loaded because of an invalid enumeration value '%{enumValue/}' for member '%{memberName/}' in object ...
- The data model has a very long calculated table dependency chain that is likely a loop. Please check the calculated table ...
- The data model has a very long calculated table dependency chain, which likely indicates a loop. Please check the calculated ...
- The data model has encountered an unexpected inconsistency and cannot be loaded. The column partition file names '%{file1/}' ...
- The data model has encountered an unexpected inconsistency and cannot be loaded. The dictionary storage type for column '%{col/}' ...
- The data model has encountered an unexpected inconsistency and cannot be loaded. The system table '%{IMBITableId/}' is expected ...
- The data model in this workbook is currently being upgraded. Upgrading the data model may take some time. You can cancel ...
- The data processing extension used for this data source is not available. It has either been uninstalled, or it is not configured ...
- The data provider was unable to convert the value '%{variant/}' from the source data type '%{vartype/}' to the expected data ...
- The data reader is incompatible with the specified '{0}'. A member of the type, '{1}', does not have a corresponding column ...
- The data reader is incompatible with the specified function mapping, and the type of a row could not be determined for the ...
- The data refresh job failed to update the PowerPivot workbook because another user modified the file while data refresh was ...
- The data shape {1}' has only a single member hierarchy but specifies {2} data rows. If only a single member hierarchy is ...
- The data source '{0}' uses a custom data processing extension which does not implement IDbConnectionExtension. Therefore, ...
- The data source '{0}' uses a managed data provider which does not implement IDbConnectionExtension. Only Windows Integrated ...
- The data source is configured to prompt for credentials but no prompt text has been entered. Enter prompt text for the data ...
- The data source may might not be accessible from the location where the report was saved. The report was saved to "{0}". ...
- The data source table with id '{0}' was not found while adding to the repository. Check whether the table is accessible by ...
- The data source view does not contain a definition for the '%{table/}' table or view. The Source property may not have been ...
- The data source view for the cube does not contain some tables, named calculations, primary keys, or relationships used by ...
- The data source {1}' has both or neither of the following: DataSourceReference and ConnectionProperties. DataSource must ...
- The Data Streaming Destination component could not connect to Microsoft OLE DB Provider for SQL Server Integration Services ...
- The Data Streaming Destination component failed to execute because another Data Streaming Destination component is currently ...
- The data synchronization state of this availability database is unhealthy. On an asynchronous-commit availability replica, ...
- The data tap '%1!s!' does not exist, or you do not have sufficient permissions to remove it. Provide a valid data tap ID. ...
- The data type "%1!s!" cannot be compared. Comparison of that data type is not supported, so it cannot be sorted or used as ...
- The data type "%1!s!" cannot be used with binary operator "%2!s!". The type of one or both of the operands is not supported ...
- The data type "%1!s!" cannot be used with unary operator "%2!s!". This operand type is not supported for the operation. To ...
- The data type "%1!s!" found on column "%2!s!" is not supported for the %3!s!. This column will be converted to DT_NTEXT. ...
- The data type "%1!s!" is invalid for transaction names or savepoint names. Allowed data types are char, varchar, nchar, varchar(max), ...
- The data type %1!s! cannot be used as an operand to the UNION, INTERSECT or EXCEPT operators because it is not comparable. ...
- The data type %1!s! does not exist. Verify the supported data types and mappings by querying msdb.dbo.sysdatatypemappings. ...
- The data type %1!s! is invalid for the %2!s! function. Allowed types are: char/varchar, nchar/nvarchar, and binary/varbinary. ...
- The data type cannot be changed to a new data type; the column contains values that don't conform to the data type selected ...
- The data type conversion file, {0}, cannot be located. Therefore, the wizard cannot provide information about the conversion ...
- The data type for "%1!s!" is DT_IMAGE, which is not supported. Use DT_TEXT or DT_NTEXT instead and convert the data from, ...
- The data type for "%1!s!" is DT_NTEXT, which is not supported with ANSI files. Use DT_TEXT instead and convert the data to ...
- The data type for "%1!s!" is DT_TEXT, which is not supported with Unicode files. Use DT_NTEXT instead and convert the data ...
- The data type is about to be changed for the column. This will affect how the data is stored and might impact data precision ...
- The data type mapping for %1!s! does not exist. Verify the list of available mappings by querying msdb.dbo.sysdatatypemappings. ...
- The data type of a foreign key binding (ordinal=%{iOrdinal/}) for the '%{tablecolumn/}' nested table does not match the data ...
- The data type of the '%{measure/}' measure must be the same as its source data type. This is because the aggregate function ...
- The data type of the '%{structure/}.'%{dmscolumn/}' mining structure column must be numeric since it has a continuous content ...
- The data type of the parameter "{0}" is {1}. However, one or more of the values provided for the parameter cannot be converted ...
- The data type of the parameter "{0}" is {1}. However, the value provided for the parameter cannot be converted to this type. ...
- The data type of the {0} named calculation will be changed, and the following associated relationships will be removed:'{1}' ...
- The data type specified for column '%1!s!' in table '%2!s!' cannot be used as a column in the distribution key of an index. ...
- The data type specified for the '%{column/}' column of the '%{structure/}' OLAP mining structure is not compatible with its ...
- The data types "%1!s!" and "%2!s!" are incompatible for binary operator "%3!s!". The operand types could not be implicitly ...
- The data types "%1!s!" and "%2!s!" are incompatible for the conditional operator. The operand types cannot be implicitly ...
- The data types char(n) and varchar(n) using a collation that has a code page other than 1252 are not supported with %1!s!. ...
- The data types of the operands of the conditional operator were incompatible. The operand types could not be implicitly cast ...
- The data types varchar(max), nvarchar(max), varbinary(max), and XML cannot be used in the compute clause by client driver ...
- The data-tier application cannot be upgraded because the database associated with the data-tier application is not available. ...
- The data-tier application was deleted from the instance. Refresh the Object Explorer pane before selecting a data-tier application. ...
- The database "%1!s!" does not exist. RESTORE can only create a database when restoring either a full backup or a file backup ...
- The database "%1!s!" is already configured for database mirroring on the remote server. Drop database mirroring on the remote ...
- The database "%1!s!" is in warm-standby state (set by executing RESTORE WITH STANDBY) and cannot be backed up until the entire ...
- The database '%1!s!' at the redirected publisher '%2!s!' for original publisher '%3!s!' and database '%4!s!' belongs to a ...
- The database '%1!s!' at the redirected publisher '%2!s!' for original publisher '%3!s!' and database '%4!s!' is either not ...
- The database '%1!s!' cannot be enabled for Change Data Capture because a database user named 'cdc' or a schema named 'cdc' ...
- The database '%1!s!' cannot be opened because it is version %2!s!. This server supports version %3!s! and earlier. A downgrade ...
- The database '%1!s!' cannot be removed from availability group '%2!s!'. This database does not belong to the availability ...
- The database '%1!s!' contains REMOTE_DATA_ARCHIVE tables, it will be marked as disconnected from the remote during the restore. ...