SQL Server 2012

  1. CREATE INDEX statement failed because specifying %1!s! is not allowed when creating a columnstore index. Consider creating ...
  2. CREATE INDEX statement failed because specifying DATA_COMPRESSION is not allowed when creating a columnstore index. Consider ...
  3. CREATE INDEX statement failed because specifying FILESTREAM_ON is not allowed when creating a columnstore index. Consider ...
  4. CREATE INDEX statement failed because specifying key list is missing when creating an index. Create the index with specifying ...
  5. CREATE INDEX statement failed because specifying sort order (ASC or DESC) is not allowed when creating a columnstore index. ...
  6. CREATE INDEX statement failed because table '%1!s!' uses vardecimal storage format. A columnstore index cannot be created ...
  7. CREATE INDEX statement failed because the %1!s! option is not allowed when creating a columnstore index. Create the columnstore ...
  8. CREATE INDEX statement failed. A columnstore index cannot include a datetimeoffset data type with a precision greater than ...
  9. CREATE INDEX statement failed. A columnstore index cannot include a decimal or numeric data type with a precision greater ...
  10. CREATE INDEX statement failed. Column '%1!s!' is either a primary key or a partitioning key that must be included, but '%2!s!'has ...
  11. CREATE INDEX statement failed. Column '%1!s!' is either a primary key or a partitioning key that must be included, but a ...
  12. CREATE INDEX statement failed. Column '%1!s!' is either a primary key or a partitioning key that must be included, but a ...
  13. CREATE INDEX statement failed. Column '%1!s!'has a data type that cannot participate in a columnstore index. Omit column ...
  14. CREATE INDEX statements with a DROP_EXISTING option are not supported in a data-tier application. Remove the statement or ...
  15. CREATE LOGIN statements with DEFAULT_DATABASE option are not supported in a data-tier application. Remove the statement or ...
  16. CREATE LOGIN statements with PASSWORD or SID options that do not specify a MUST_CHANGE option are not supported in a data-tier ...
  17. Create or edit perspectives to define views of the PowerPivot data. Before you can create perspectives, at least one table ...
  18. CREATE PROCEDURE statements with cursor parameters are not supported in a data-tier application. Remove the statement or ...
  19. CREATE PROCEDURE statements with ENCRYPTION option are not supported in a data-tier application. Remove the statement or ...
  20. CREATE RULE and DROP RULE will be removed in a future version of SQL Server. Avoid using CREATE RULE and DROP RULE in new ...
  21. CREATE SCHEMA statements that contain schema elements are not supported in a data-tier application. Remove the elements from ...
  22. CREATE TRIGGER statements for DDL triggers are not supported in a data-tier application. Remove the statement before rebuilding. ...
  23. CREATE TRIGGER statements with ENCRYPTION option are not supported in a data-tier application. Remove the statement or ENCRYPTION ...
  24. CREATE USER statements with the DEFAULT_LANGUAGE or PASSWORD option are not supported in a data-tier application. Remove ...
  25. CREATE VIEW statements with ENCRYPTION option are not supported in a data-tier application. Remove the statement or ENCRYPTION ...
  26. Create, view, or delete relationships between tables in the PowerPivot window. Before you can manage relationships, at least ...
  27. CREATE/ALTER ENDPOINT cannot be used to update the endpoint with this information. The Dedicated Administrator Connection ...
  28. CREATE/ALTER/DROP DATABASE ENCRYPTION KEY failed because a lock could not be placed on database '%1!s!'. Try again later. ...
  29. createpackage Create an XML package file for the specified model. Usage: MDSModelDeploy createpackage -package -model -version ...
  30. Creates a multidimensional and data mining project by extracting the metadata from an existing multidimensional and data ...
  31. Creates a new mining model based on an existing mining structure, and saves the model in a temporary file. Specifies the ...
  32. Creates a new mining model that is based on an existing mining structure, specifies the algorithm to use for analysis, and ...
  33. Creates a new mining structure on the current instance of Analysis Services and optionally define a percentage of the data ...
  34. Creates a prediction by mapping an existing mining model to an external data source and then filtering the input data by ...
  35. Creates a prediction on a mining model that contains a nested table, by using an external data source that also contains ...
  36. Creates a prediction on a mining model that contains a nested table, by using an external data source that also contains ...
  37. Creates a query that returns information about an existing mining model, or about the patterns and statistics in the data. ...
  38. Creates and populates an in-memory ADO recordset that is available outside of the data flow. Scripts and other package elements ...
  39. Creates new column values by applying expressions to transformation input columns. Create new columns or overwrite existing ...
  40. Creates or rebuilds indexes for all processed partitions. This option results in no operation on unprocessed objects. This ...
  41. Creates or upgrades a management data warehouse for storing data collection set results. To configure data collection for ...
  42. Creating a %1!s! index requires that the primary key in the base table satisfy the following restrictions. The maximum number ...
  43. Creating a new database for the users of the Data Mining Add-ins for Office 2010 gives them the freedom to create temporary ...
  44. Creating a UCP on the specified instance of SQL Server will provision the UCP schema, jobs, and policies, and enable the ...
  45. Creating and altering SOAP endpoints will be removed in a future version of SQL Server. Avoid using this feature in new development ...
  46. Creating and scheduling a worker task for AlwaysOn Availability Groups failed due to lack of resources (SQL OS error %1!s!). ...
  47. Creating or altering compressed table '%1!s!' failed because the uncompressed row size would be %2!s!, including %3!s! bytes ...
  48. Creating or altering table '%1!s!' failed because the minimum row size would be %2!s!, including %3!s! bytes of internal ...
  49. Creating publications from heterogeneous data sources is supported only on servers running Microsoft SQL Server 2005 and ...
  50. Creating the SQL Server Browser service with the following parameters: Display Name: '{0}', Service Type: '{1}', Start Type: ...
  51. Creation of a TSQL endpoint will result in the revocation of any 'Public' connect permissions on the '%1!s!' endpoint. If ...
  52. Creation of the full-text index is not available. Check that you have the correct permissions or that full-text catalogs ...
  53. Credentials cannot be used with the FILESTREAM Provider. Remove any credential entries that are associated with this blob ...
  54. Credentials must be specified before the report can be displayed. Enter credentials in the credentials area and click the ...
  55. Croatian, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server Sort Order ...
  56. Croatian, case-sensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server Sort Order ...
  57. Cryptographic provider %1!s! '%2!s!' in dll is different from the guid recorded in system catalog for provider with id %3!s!. ...
  58. Cryptographic provider is now disabled. However users who have an open cryptographic session with the provider can still ...
  59. Cryptographic provider is now dropped. However users who have an open cryptographic session with the provider can still use ...
  60. Cryptographic provider library '%1!s!' loaded into memory. This is an informational message only. No user action is required. ...
  61. CSN being added must be equal or greater than the last CSN. The new CSN is (%1!s!,%2!s!), the current CSN is (%3!s!,%4!s!). ...
  62. CSN vector can be reinitialized only with initial or invalid CSN. The new CSN is (%1!s!,%2!s!), the current CSN is (%3!s!,%4!s!). ...
  63. CTI violation on Enqueue. The current event timestamp of '{0:o}' is less than the last enqueued CTI timestamp of '{1:o}'. ...
  64. CTI violation on the output of a published stream. The current event timestamp of '{0:o}' is less than the last CTI timestamp ...
  65. Cube attribute binding for property '%{property_name/}' is invalid because the parent dimension has a different source cube ...
  66. Cube attribute binding for property '%{property_name/}' is invalid because the parent dimension has a different source cube. ...
  67. Cube attribute {0} can not be used as a mining structure column because its attribute hierarchy is not enabled. You can enable ...
  68. Cube Wizard has analyzed the relationships between tables in the data source view to identify fact tables and dimensions. ...
  69. CubeDimensionPermission object is not supported for Business Intelligence Semantic Model databases running on an Analysis ...
  70. Culture expression '{0}' is not directly supported in a LINQ query. Assign it to a local variable and then use the variable ...
  71. Cumulative I/O performed by this session since it connected ("sys.dm_exec_sessions.reads" plus "sys.dm_exec_sessions.writes") ...
  72. Current number of threads waiting for a latch. These are latch requests that could not be given immediate grants and are ...
  73. current scan started from this LSN, available after at beginning of phase 2, DMV users should call PackLSN(.) before display ...
  74. Current selection has inconsistent action options. Select one of the options below to apply the same action to the whole ...
  75. Current selection includes areas with the different types of markup. Select one of the options below to set a new markup ...