SQL Server 2012
- The database default collation '%1!s!' is case sensitive and cannot be used to create a FileTable. Specify a case insensitive ...
- The Database Email feature is not turned on for this SQL Server instance. To turn on the feature and create a new database ...
- The Database Engine instance you selected is not valid for this edition of Reporting Services. The Database Engine does not ...
- The Database Engine is attempting to release a group of locks that are not currently held by the transaction. Retry the transaction. ...
- The Database Engine received a floating point exception from the operating system while processing a user request. Try the ...
- The Database Engine service could not resolve the specified file location. Either the location does not exist, or the current ...
- The Database Engine service could not resolve the specified folder location. Either the location does not exist, or the current ...
- The database file "%1!s!" is already used by the source database. Source and destination databases cannot use the same database ...
- The database file with name '{0}' already exists in directory '{1}'. Make sure there is no existing database file with the ...
- The database file with name '{0}' is not found under DTS directory. Make sure the database file exists under this directory ...
- The database folder '%{detach_log_location/}' does not exist, is too long, or contains characters that are not valid or are ...
- The database has been rolled forward to the end of this backup set and beyond the specified point in time. RESTORE WITH RECOVERY ...
- The database has reached its size quota. Partition or delete data, drop indexes, or consult the documentation for possible ...
- The Database ID %1!s!, Page %2!s!, slot %3!s! for LOB data type node does not exist. This is usually caused by transactions ...
- The database is attached from a subscription copy file without using sp_attach_subscription. Drop the database and reattach ...
- The database is currently being used by another thread under the same workspace in exclusive mode. The operation failed. ...
- The database is not valid due to the following errors: {0} Aggregation can only be designed for a valid database. Please ...
- The database is using the simple recovery model. The data in the backup it is not consistent with the current state of the ...
- The database mail profile, {0}, does not exist on the selected database server. The profile has been removed from the system ...
- The database maintenance plan {0} contains log shipping settings. Those settings were not migrated to the new maintenance ...
- The database management system (DBMS) %1!s! %2!s! does not exist. Verify the supported DBMS and versions by querying msdb.dbo.MSdbms. ...
- The database mirroring feature is deprecated and will be removed in a future version of SQL Server. Avoid using this feature ...
- The database mirroring safety level must be FULL to manually failover database "%1!s!". Set safety level to FULL and retry. ...
- The database mirroring service cannot be forced for database "%1!s!" because the database is not in the correct state to ...
- The database name is missing. To add the name, right click on the Project name, select Properties, and then enter a database ...
- The database owner SID recorded in the master database differs from the database owner SID recorded in database '%1!s!'. ...
- The database principal '%1!s!' cannot be used in a remote service binding because it cannot own certificates. Remote service ...
- The database principal '%1!s!' cannot be used in a remote service binding because it cannot own certificates. This is a special ...
- The database principal is set as the execution context of one or more procedures, functions, or event notifications and cannot ...
- The Database Publishing Wizard allows you to generate scripts for databases and objects inside of databases. This wizard ...
- The database schema requires a newer version of the client library ({1}). The current library is ({0}). Install the required ...
- The database schema version for the FILESTREAM blob store is . This version is earlier than version , which is the minimum ...
- The database snapshot for online checks could not be created. Either the reason is given in a previous error or one of the ...
- The database to be restored was named '%1!s!'. Reissue the statement using the WITH REPLACE option to overwrite the '%2!s!' ...
- The database was backed up on a server running version %1!s!. That version is incompatible with this server, which is running ...
- The database with ID '%{dbid/}' cannot be altered from ReadWrite to ReadOnly or vice versa. The ReadWriteMode property cannot ...
- The database with ID '%{dbid/}' cannot be created with ReadWriteMode set to ReadOnly. A database can only be created in ReadWrite ...
- The database with name '%{DBName/}', ID '%{DBId/}' cannot be restored since it already exists on the server and is read-only. ...
- The database with name '%{DBName/}', ID '%{DBId/}' cannot be synchronized since it already exists on the target server and ...
- The database within this workbook was created by a newer version of PowerPivot (version: '%{compLevel/}') and cannot be opened. ...
- The database you have selected is configured for Reporting Services SharePoint mode. Please select a SQL Server database ...
- The database you have selected is not a report server database. Please select a SQL Server database that contains report ...
- The database {0} exists on the SQL Server. You must choose a different database or install Reporting Services into existing ...
- The DataPoint {2} in the {0} {1}' has the name "{3}". DataValue names cannot be null and must be unique within the DataValues ...
- The DataPoints in the {0} {1}' has an invalid set of {2} items. {2} names must be unique within the {2} collection for the ...
- The dataset '{0}' has no spatial fields. Enter the name of a dataset with a field that is data type SqlGeography or SqlGeometry. ...
- The dataset cannot be generated. An error occurred while connecting to a data source, or the query is not valid for the data ...
- The dataset {1}' refers to the shared data set {3}', which is not published on the report server. The shared data set {3}' ...
- The dataset {1}' refers to the shared data source {3}', which is not published on the report server. The shared data source ...
- The datasource '%{datasource/}' requires an isolation level of SnapshotIsolation which is not supported by the database provider. ...
- The datasource in the current set of out-of-line bindings, '%{Datasource/}', contains an ImpersonationMode that cannot be ...
- The DataSource property of the specified DataGridView is not set to a BindingSource with a SupportsFiltering property value ...
- The DataSourceID of the ReportDataSource '{0}' of the ReportViewer '{1}' must be the ID of a control of type IDataSource. ...
- The DataSourceID of the ReportDataSource '{0}' of the ReportViewer '{1}' must be the ID of a control of type IDataSource. ...
- The DatastoreDocumentCondition element cannot be the root element of a document, it can only be used as the child of a Condition ...
- The DatastoreFlagCondition element cannot be the root element of a document, it can only be used as the child of a Condition ...
- The DatastoreProperties element cannot be the root element of a document, it can only be used as the child of an Action element. ...
- The DataType element of the binding for a mining structure column, whose content type is set to Date, must be also set to ...
- The datatype of the identity column of table '%1!s!' is tinyint. tinyint does not have enough numbers available for merge ...
- The DataType property for the {0} is {2}, but the default value Expression for "{1}" returns the data type {3}. The data ...
- The DataType property for the {0} is {2}, but the Expression for "{1}" returns the data type {3}. The DataType property for ...
- The DataType property for the {0} is {2}, but the {1} has the data type {3}. The DataType property for the Attribute must ...
- The DataTypeCompatibility property of ADO type connection manager "%1!s!" was set to 80 for backward compatibility reasons. ...
- The DataTypeCompatibility property of ADO type connection manager "{0}" was set to 80 for backward compatibility reasons. ...
- The DATA_COMPRESSION option was specified more than once for the table, or for at least one of its partitions if the table ...
- The date frequency level is required. If you do not want it to be visible, you can hide this attribute in the dimension editor. ...
- The date part parameter specified for function "%1!s!" is not valid. It must be a static string. The date part parameter ...
- The date provided is before the start of the Hijri calendar which in Microsoft's 'Kuwaiti Algorithm' is July 15th, 622 C.E. ...
- The date/time is converted to the RFC1123 standard format. It follows the custom pattern 'ddd, dd MMMM yyyy HH:mm:ss G\MT'. ...
- The date/time is converted to the universal full format. Pattern is always the same regardless of culture or format provider. ...
- The date/time is converted to the universal sortable format. Pattern is always the same regardless of culture or format provider. ...
- The datediff function resulted in an overflow. The number of dateparts separating two date/time instances is too large. Try ...
- The DAX formula for calculated column {1} in table {0} contains functions that are not supported for a model in DirectQuery ...
- The DBCC NEWALLOC, DBCC ROWLOCK, DBCC TEXTALL, and DBCC TEXTALLOC commands were previously announced as deprecated and have ...
- The DBMS type or version of "%1!s!" is not supported. A connection to Microsoft SQL Server version 8.0 or later is required. ...