SQL Server 2012

  1. Cannot use a retention period unit other than "days" for publication "%1!s!" because the compatibility level of the publication ...
  2. Cannot use a value of TRUE for the parameter @ignore_distributor. The value must be FALSE for a non-SQL Server Publisher. ...
  3. Cannot use alias type with rule or default bound to it as a column type in table variable or return table definition in table ...
  4. Cannot use ALTER LOGIN with the ENABLE or DISABLE argument for a Windows group. GRANT or REVOKE the CONNECT SQL permission ...
  5. Cannot use column of type image, ntext, xml, CLR type, varchar(max), nvarchar(max), or varbinary(max) in a subset or join ...
  6. Cannot use file '%1!s!' because it was originally formatted with sector size %2!s! and is now on a volume with sector size ...
  7. Cannot use file '%1!s!' for clustered server. Only formatted files on which the cluster resource of the server has a dependency ...
  8. Cannot use file '%1!s!', because it is on a volume with sector size %2!s!. SQL Server supports a maximum sector size of 4096 ...
  9. Cannot use object '%1!s!' with autodrop object attribute in schemabinding expressions because it is a system generated view ...
  10. Cannot use partition groups because one or more filters reference the following view, which contains functions: "%1!s!". ...
  11. Cannot use partition groups because the join filter between the following articles contains one or more functions: "%1!s!" ...
  12. Cannot use partition groups with unfiltered publications. Set "use_partition_groups" to "false" using sp_changemergepublication. ...
  13. Cannot use qualified table names (schema or catalog) with the OLE DB provider "%1!s!" for linked server "%2!s!" because it ...
  14. Cannot use table option LARGE VALUE TYPES OUT OF ROW on a user table that does not have any of large value types varchar(max), ...
  15. Cannot use TEXTIMAGE_ON when a table has no text, ntext, image, varchar(max), nvarchar(max), non-FILESTREAM varbinary(max), ...
  16. Cannot use the backup file '%1!s!' because it was originally formatted with sector size %2!s! and is now on a device with ...
  17. Cannot use the following options with a Columnstore index: PAD_INDEX ,STATISTICS_NORECOMPUTE ,SORT_IN_TEMPDB ,IGNORE_DUP_KEY ...
  18. Cannot use the INSERT command because the table has an identity column. The insert custom stored procedure must be used to ...
  19. Cannot use the specified data type mapping. The matching destination data type for source type %1!s! cannot be found. Query ...
  20. Cannot use the volume on device '%1!s!' as a continuation volume. It is sequence number %2!s! of family %3!s! for the current ...
  21. Cannot use transaction marks on database '%1!s!' with bulk-logged operations that have not been backed up. The mark is ignored. ...
  22. Cannot validate argument '{0}' on parameter 'DhcpSubnet'. The argument must be in the format / (for example, 192.168.0.0/255.255.255.0). ...
  23. Cannot validate argument '{0}' on parameter 'StaticIp'. The argument must be in the format / (for example, 192.168.0.0/255.255.255.0), ...
  24. Cannot verify administrator login privileges for Oracle Publisher %1!s!. Verify connection information and ensure that you ...
  25. Cannot write into file '%1!s!'. Verify that you have write permissions, that the file path is valid, and that the file does ...
  26. Cannot write to the message queue for the queued updating subscription. Ensure that Microsoft Distributed Transaction Coordinator ...
  27. Cannot write to the script file in the snapshot folder at the Distributor (%1!s!). Ensure that there is enough disk space ...
  28. Canonicalization did not find a non empty x-ms-date header in the WebRequest. Please use a WebRequest with a valid x-ms-date ...
  29. Capture instance name '%1!s!' exceeds the length limit of 100 characters. Specify a name that satisfies the length constraint. ...
  30. Capture instance name '%1!s!' is invalid. Specify a valid name. See the topic 'Identifiers' in SQL Server Books Online for ...
  31. Cardinality reduction has been applied on column, %{colname/} of model, %{modelname/} due to the large number of states in ...
  32. Cardinality reduction has been applied on column, %{colname/} of model, %{modelname/} due to the large number of states in ...
  33. Case processor detects repeated KeyTime values ('time stamps') applicable to the same Time Series while processing data for ...
  34. Catalog or schema name of XML schema collection can not be specified without specifying the name of XML schema collection. ...
  35. Causes the Pivot Transform to ignore rows containing unrecognized values in the Pivot Key column and to report the complete ...
  36. Caution: sys.sql_dependencies shows that other objects (views, procedures and so on) are referencing this object by its old ...
  37. Caution: {0} asserts that this content is safe. This SSIS package should be opened only if you trust {0} to make that assertion. ...
  38. Ca[llerInfo Optional. Ignored when running dtexec from the command line. Use this option when scheduling a job with SQL Agent ...
  39. CellPermission object is not supported for Business Intelligence Semantic Model databases that run on an Analysis Services ...
  40. CepUtility.DoNotCall()' method is only used by the extension method defined on CepWindow for a user-defined operator or aggregate. ...
  41. Chain sequence numbers are out of order in the Index Allocation Map (IAM) chain for object ID %1!s!, index ID %2!s!, partition ...
  42. Change Data Capture cannot proceed with the job-related action because transactional replication is enabled on database %1!s! ...
  43. Change data capture has not been enabled for source table '%1!s!.%2!s!'. Specify the name of a table enabled for Change Data ...
  44. Change Data Capture has scanned the log from LSN{%1!s!} to LSN{%2!s!}, %3!s! transactions with %4!s! commands have been extracted. ...
  45. Change data capture instance '%1!s!' has not been enabled for the source table '%2!s!.%3!s!'. Use sys.sp_cdc_help_change_data_capture ...
  46. Change Data Capture population failed writing blob data for one or more large object columns. Verify that SQL Server has ...
  47. Change the authentication type, account, or password that the Master Data Services (MDS) service account uses to connect ...
  48. Change the authentication type, account, or password that the report server uses to connect to the report server database. ...
  49. Change the data type for the column. Changing the data type affects how the data is stored. You must select the columns whose ...
  50. Change the default behavior of different visualization types and default grouping behavior in client tools for this table. ...
  51. Change the default selection and ordering of columns and measures of this table when it is added to a report in a reporting ...
  52. Change tracking is disabled for database '%1!s!'. Change tracking must be enabled on a database to modify change tracking ...
  53. Change tracking is enabled for one or more tables in database '%1!s!'. Disable change tracking on each table before disabling ...
  54. Changes have been made to the mining structure. Do you want to reprocess the mining structure and all its related models? ...
  55. Changes made to cube storage settings will not affect existing measure groups. The new settings will be used as defaults ...
  56. Changes made to measure group storage settings will not affect existing partitions. The new settings will be used as default ...
  57. Changes made to subscription data since the last synchronization will be lost unless the changes are uploaded before the ...
  58. Changes to server properties and settings may affect the performance, security, and availability of this SQL Server instance. ...
  59. Changes to SQL dumper configuration will take effect when the collection set is restarted. To perform an immediate dump, ...
  60. Changes to the state or options of database '%1!s!' cannot be made at this time. The database is in single-user mode, and ...
  61. Changes were made in the database while you were working. Do you want to update the database and override those changes to ...
  62. Changes were made in the database while you were working. The script will contain changes that will update the database and ...
  63. Changing a column data type results in an index that is too large. Changing the data type of column ' ' on table ' ' from ...
  64. Changing Subscriber types changes the compatibility level of this publication and changes whether certain publication and ...
  65. Changing the column to the selected datatype will delete its indexes and all relationships it participates in. Do you want ...
  66. Changing the column to the selected datatype will delete its indexes. Do you want to change the datatype and delete the indexes? ...
  67. Changing the column to the selected datatype will delete its spatial indexes. Do you want to change the datatype and delete ...
  68. Changing the column to the selected datatype will delete its xml indexes. Do you want to change the datatype and delete the ...
  69. Changing the column to the selected datatype will delete relationships with the following tables: . Do you want to change ...
  70. Changing the data type from XML will result in the XML indexes associated with this column to be deleted. Do you want to ...
  71. Changing the database compatibility level has caused data to be marked as unchecked in one or more objects in database %1!s!. ...
  72. Changing the of this object will result in all current permissions on this object being dropped. Are you sure you want to ...
  73. Changing the Project Deployment Model requires that the whole solution be closed and then reopened. Any unsaved changes within ...
  74. Changing the report parameters or data sources to the values you specified is not allowed. The report is configured to run ...
  75. Changing the status to %1!s! for full-text catalog '%2!s!' (%3!s!) in database '%4!s!' (%5!s!). This is an informational ...