SQL Server 2012

  1. The option that is used to reset the connection. This field is available only for reset connection remote procedure calls. ...
  2. The option that was used to reset the connection. This field is available only for reset connection remote procedure calls. ...
  3. The option {0} is set to true for primary key defined on the table {1}. This option is not supported in the target database ...
  4. The options on this page only apply when the frame shape is set to "Circular", "Rectangular", "Rounded rectangular" or "Auto ...
  5. The options you have selected are not secure. The user name and password will be sent as plain text to the specified Web ...
  6. The OPTMIZED_PREDICTION_COUNT parameter for the '%{modelname/}' model is not supported. OPTMIZED_PREDICTION_COUNT must be ...
  7. The Oracle INSTR(string, substring) function can be converted to a SQL Server CHARINDEX function call, or to a call to the ...
  8. The Oracle INSTR(string, substring, position) function can be converted to SQL Server CHARINDEX function call or call to ...
  9. The Oracle Publisher name is '%1!s!' and the Oracle Subscriber name is '%2!s!'. Bidirectional Oracle publishing requires ...
  10. The Oracle Publisher support package could not be loaded. Drop the replication administrative user schema and re-create it; ...
  11. The Oracle server %1!s! is already defined as the Publisher %2!s! on the Distributor %3!s!].[%4!s!]. Drop the Publisher or ...
  12. The Oracle SUBSTR(string, portion, substring_length) function can be converted to SQL Server SUBSTRING function call, or ...
  13. The ORDER BY clause is invalid in views, inline functions, derived tables, subqueries, and common table expressions, unless ...
  14. The ORDER BY clause is not valid in views, inline functions, derived tables, sub-queries, and common table expressions, unless ...
  15. The order of the columns was not specified in the object that created the rowset. The provider had to reexecute the command ...
  16. The order of the data in the data file does not conform to the ORDER hint specified for the BULK rowset '%1!s!'. The order ...
  17. The order of the data in the stream does not conform to the ORDER hint specified for the CLR TVF '%1!s!'. The order of the ...
  18. The original file name '%1!s!' for logical database file '%2!s!' is too long to be combined with the full path to the new ...
  19. The output column "%1!s!" (%2!d!) on output "%3!s!" (%4!d!) and component "%5!s!" (%6!d!) is not subsequently used in the ...
  20. The output column with lineage ID "%1!d!" is incorrectly mapped to an input column. The CopyColumnId property of the output ...
  21. The output columns' metadata does not match the associated input columns' metadata. The output columns' metadata will be ...
  22. The output field expression for field '{0}' has an invalid type for argument number {1} - expected type '{3}', actual type ...
  23. The output file cannot be appended. Column "%1!s!" matches by name, but the column in the file has code page %2!d! and the ...
  24. The output file cannot be appended. Column "%1!s!" matches by name, but the column in the file has maximum length %2!d! and ...
  25. The output file cannot be appended. Column "%1!s!" matches by name, but the column in the file has precision %2!d! and the ...
  26. The output file cannot be appended. Column "%1!s!" matches by name, but the column in the file has scale %2!d! and the input ...
  27. The output file cannot be appended. Column "%1!s!" matches by name, but the column in the file has type %2!s! and the input ...
  28. The output file was written by an incompatible version and cannot be appended. The file may be an older file format that ...
  29. The output name cannot be changed. There is the dangling output, which is not shown in the list of available outputs, with ...
  30. The output with ID %1!d! of Aggregate component is not used by any component. Please either remove it or associate it with ...
  31. The OutputPath property cannot be blank. It must provide a relative path that is a child folder under the path of the report ...
  32. The package "{0}" already exists on the server. Do you want to overwrite the package at destination? Click Yes to overwrite ...
  33. The package %1!s! can not be saved to the file system since its protection level is server storage. Use the encrypt action ...
  34. The package cannot be loaded because the state of the digital signature violates signature policy. Error 1!8.8X! "%2!s!" ...
  35. The package cannot be loaded. The package file is corrupt or the package was created by using an earlier version of Master ...
  36. The package cannot be loaded. This occurs when attempting to load an older version package, or the package file refers to ...
  37. The Package Configuration Wizard helps you create configurations which can be used to dynamically configure the package during ...
  38. The package contains data flow components with multiple inputs. Run-time dependencies that exist among these components may ...
  39. The package contains one or more event handlers for this task. Deleting the task will also delete the event handlers and ...
  40. The package failed during execution because the checkpoint file cannot be loaded. Further execution of the package requires ...
  41. The package file '{0}' is missing from the project directory. Move the package to the same directory as the project file ...
  42. The package file '{0}' is missing from the project directory. The project will persist without this package. To resolve the ...
  43. The package file '{0}' is missing from the project directory. This package has been skipped, and project will continue to ...
  44. The package file '{0}' is missing from the project directory. To resolve the problem, exclude the package from the project ...
  45. The package has been migrated to a later version during loading. It must be reloaded to complete the process. This is an ...
  46. The package id {0} used to determine the localized description of a failing component is unknown, which prevents a FeatureError ...
  47. The package is currently running in debug mode; the changes made to the package will not take effect until the package is ...
  48. The Package Migration Wizard migrates packages created using previous versions of SQL Server tools and object models to SQL ...
  49. The Package Migration Wizard requires the SQL Server 2000 Data Transformation Services (DTS) runtime. To install the DTS ...
  50. The package name, {0}, contains characters that are not valid. The following characters are not valid: \ / : . ? " < > | ...
  51. The package path and data flow path ID strings already exist for the execution ID %1!s!. Provide package path and data flow ...
  52. The package path referenced an object that cannot be found: "%1!s!". This occurs when an attempt is made to resolve a package ...
  53. The package was digitally signed, but the signature is not valid. The contents of the package could have been modified by ...
  54. The package will still be able to load normally but the previous layout information will be lost and the designer will automatically ...
  55. The packages shown below contain Execute Package tasks. It's recommended that you let the wizard change each of these Execute ...
  56. The page %1!s!, object ID %2!s!, index ID %3!s!, partition ID %4!s!, allocation unit ID %5!s! (type %6!s!) has been modified, ...
  57. The PageName property specified on the data region, rectangle, or group {0}' was removed from the report. SQL Server 2008 ...
  58. The PageName property was detected in the data region, rectangle, or group {0}' SQL Server 2008 Reporting Services does not ...
  59. The parameter "%1!s!" cannot be found. This error occurs when an attempt to retrieve a parameter from a parameters collection ...
  60. The parameter "%1!s!" is not the same type as the type it was created with. Drop and recreate the module using a two-part ...
  61. The parameter "{0}" is configured to use an environment variable, but no environment has been selected. Check the "Environment" ...
  62. The parameter "{0}" is configured to use an environment variable, but no environment has been selected. Select the "Environment" ...
  63. The parameter "{0}" references variable "{2}", which is not provided by project defaults. Choose a running environment that ...
  64. The parameter %1!s! cannot be provided for users that cannot authenticate in a database. Remove the WITHOUT LOGIN or PASSWORD ...
  65. The parameter %1!s! is not supported for non-SQL Server publications. The value specified for this parameter must be %2!s!. ...
  66. The parameter '%1!s!' was deduced to be a table-valued parameter, which cannot be sent by client driver versions earlier ...
  67. The parameter '%1' cannot be specified because at least one publication already exists in this publication database that ...
  68. The parameter '{0}' does not allow multiple values. Change the parameter settings to allow multiple values or enclose the ...
  69. The parameter @supports_net_changes is set to 1, but the source table does not have a primary key defined and no alternate ...
  70. The parameter must be 'description', 'taskid', 'sync_method', 'status', 'repl_freq', 'restricted', 'retention', 'immediate_sync', ...
  71. The parameter SITE can not be prefixed by a scheme such as 'http://'. Valid values for SITE include {'*' | '+' | 'site_name'}. ...
  72. The parameter value could not be assigned because the data types did not match. The provided value was of type "%1!s!", the ...
  73. The parameter value could not be assigned because the data types did not match. The provided value was of type '{0}'. The ...
  74. The parameter {1}' has no default. A default is required for all non-nullable parameters without a prompt or the valid values ...
  75. The parameter, '{0}', is not valid because it is not unique in the command. Combine parameters with the same name into one ...