SQL Server 2008

  1. The parameter must be 'description', 'taskid', 'sync_method', 'status', 'repl_freq', 'restricted', 'retention', 'immediate_sync', ...
  2. The parameter SITE can not be prefixed by a scheme such as 'http://'. Valid values for SITE include {'*' | '+' | 'site_name'}. ...
  3. The parameter {1}' has no default. A default is required for all non-nullable parameters without a prompt or the valid values ...
  4. The parameters @article and @join_articlename cannot have the same value. Specify different articles for the two parameters; ...
  5. The parameters for security, batch size, and scheduling have been deprecated and should no longer be used. For more information, ...
  6. The parameters given on the command line are not valid. The required command line parameters are: -PS -PD -PN -PT - publication ...
  7. The parameters given on the command line are not valid. The required command line parameters are: -S -E - if present, use ...
  8. The parameters given on the command line are not valid. The required command line parameters are: -S -E - if present, use ...
  9. The parameters given on the command line are not valid. Valid command line parameters are: -S - server on which to run the ...
  10. The parameters given on the command line are not valid. Valid command line parameters are: -S - server on which to run the ...
  11. The parameters given on the command line are not valid. Valid command line parameters are: -S - server on which to run the ...
  12. The parameters given on the command line are not valid. Valid command line parameters are: -S - server on which to run the ...
  13. The parameters given on the command line are not valid. Valid command line parameters are: -S - server on which to run the ...
  14. The Parameters property of the IDbCommand interface does not support the IList interface. External error: %1[%{exception/}%]%[;%{exceptioninner/}%]. ...
  15. The ParamValue cannot be inserted at this position. The index specified might be lesser than zero or greater than the length. ...
  16. The partition merge operation cannot be executed since it is attempting to modify the contents of the read only database ...
  17. The partition with ID '%{partitionID/}' and name '%{partitionName/}' is a regular partition and cannot be altered to be a ...
  18. The partitioned snapshot available for this Subscriber is outdated. To initialize this Subscriber, you must generate a new ...
  19. The partitioned snapshot could not be generated because the agent failed to obtain a required application lock. If the snapshot ...
  20. The partitioned snapshot process cannot complete. Cannot retrieve the maximum timestamp information from the MSsnapshot_history ...
  21. The partitioned snapshot token for this subscription is invalid and validation of the partitioned snapshot will be skipped. ...
  22. The partitioned view "%1!s!" is not updatable because one or more of the non-partitioning columns of its member tables have ...
  23. The partitions for '{0}' are not included in the project. To include the partitions, exclude the cube item from the project, ...
  24. The partitions for the cube "{0}" are not included in the project. To correct the problem, exclude the cube from the project. ...
  25. The partner server instance name must be distinct from the server instance that manages the database. The ALTER DATABASE ...
  26. The passthrough columns, "%1!s!" and "%2!s!", do not have equal data types. Only columns with equal data types are supported ...
  27. The password entered on the Administrative Password Page is invalid. Contact the Distributor administrator or try again with ...
  28. The password of login '%1!s!' is invalid. A new password should be set for this login without specifying the old password. ...
  29. The password to use in conjunction with the logon name the report server uses to impersonate when running reports unattended. ...
  30. The passwords you typed do not match. Please ensure value provided for 'Password' field matches the value provided for 'Confirm ...
  31. The patch installer has failed to update the following instance:{0}. To determine the reason for failure, review the log ...
  32. The path '%1!s!' cannot be used for FILESTREAM files. For information about supported paths, see SQL Server Books Online. ...
  33. The path '%1!s!' has invalid attributes. It needs to be a directory. It must not be hidden, read-only, or on a removable ...
  34. The path and file name of the workload file to use as input for tuning. Accepted formats: *.trc - SQL Server Profiler trace ...
  35. The path for item '{0}' exceeds the maximum length of {1}. The path includes the name of the item itself, plus the names ...
  36. The path name '{0}' is not valid. The path may not exist, you may not have permissions to access that folder, or the disk ...
  37. The path of the item '{0}' is not valid. The full path must be less than {1} characters long; other restrictions apply. If ...
  38. The path or file name '{0}' is not valid. The path may not exist, you may not have permissions to create a file in that folder, ...
  39. The path specified by '%1!s!' cannot be used for a FILESTREAM container since it is contained in another FILESTREAM container. ...
  40. The path to project folder "{0}" might be too long. Try copying the project to a shorter path (less than 98 characters long) ...
  41. The path to temporary folder "{0}" might be too long. Try setting the environment variable TMP to a shorter path (less than ...
  42. The PathName property contains the fully qualified path to the service binary file that implements the service. Example: ...
  43. The paths must refer to disks that are local to the Distributor and begin with a local drive letter and colon (for example, ...
  44. The paths to the data and log folders must refer to drives that are local to the secondary server. The paths must begin with ...
  45. The paths to the distribution database folder and transaction log folder must refer to drives that are local to '{0}'. The ...
  46. The PauseService method attempts to place the service in the paused state. It returns an integer value of 0 if the PauseService ...
  47. The peer-to-peer topology has conflict detection enabled. To add a new node into the topology, the version must be SQL Server ...
  48. The percentage of 1 MB regions of pages that have high logical fragmentation. This will be '0.00 %' for index type 'Heap.' ...
  49. The percentage of identity values to use before assigning a new range. The value must be greater than or equal to 1 and less ...
  50. The performance counter registry hive is corrupted. To continue, you must repair the performance counter registry hive. For ...
  51. The PERIODICITY_HINT parameter for the mining model, %{modelname/}, is not valid. PERIODICITY_HINT should be {n1, n2, n3.}, ...
  52. The plug-in assembly '%{plugin/}' raised the following exception when processing '%{event/}' event. %1[%{exception/}%]%[;%{exceptioninner/}%] ...
  53. The PMML-based '%{name/}' mining structure can only be altered for adding bindings to data. No other options for altering ...
  54. The point around which the needle rotates. The coordinates are in percent of the Gauge's width or height, whichever is smaller. ...
  55. The point index n ({0}) passed to STPointN is less than 1. This number must be greater than or equal to 1 and less than or ...
  56. The point-in-time clause of this RESTORE statement is restricted for use by RESTORE LOG statements only. Omit the clause ...
  57. The policy '{0}' will not be evaluated because it references a condition whose evaluation includes executing T-SQL or WQL ...
  58. The PollBegin request succeeded after %1!d! retries: 'Snapshot too old' errors encountered = %2!d!; 'Cannot Serialize Transaction' ...
  59. The PollBegin request was unable to determine a consistent set of changes and the retry maximum has been exceeded: Total ...
  60. The Polygon input is not valid because the exterior ring does not have enough points. Each ring of a polygon must contain ...
  61. The Polygon input is not valid because the interior ring number {0} does not have enough points. Each ring of a polygon must ...
  62. The Polygon input is not valid because the ring does not have enough distinct points. Each ring of a polygon must contain ...
  63. The Polygon input is not valid because the start and end points of the exterior ring are not the same. Each ring of a polygon ...
  64. The Polygon input is not valid because the start and end points of the interior ring number {0} are not the same. Each ring ...
  65. The Polygon input is not valid because the start and end points of the ring are not the same. Each ring of a polygon must ...
  66. The port specified in the connection string is not valid. The ConnectionString format is ServerName:Port. Port should be ...
  67. The posList element provided has {0} coordinates. The number of coordinates in a posList element must be an even number. ...
  68. The possible owner node '{0}' cannot be removed because it is the current owner for resource '{1}'. Move the resource to ...
  69. The precision %1!u! specified for column %2!Iu! is out of the valid range of 1 to %3!d!. InMemory Rowset creation failed. ...
  70. The predictable column has not been mapped. Open the column mapping editor and connect a column in the input table to the ...
  71. The PredictAdjustedProbability function returns the adjusted probability value for either the most likely or specified value. ...
  72. The PredictHistogram function returns a table that contains the statistics for all states of a predictable column. The table ...
  73. The PredictHistogram function returns a table that contains the statistics for cluster membership of the input case. The ...
  74. The prediction calculator is generated in a new spreadsheet, together with accuracy diagrams and a suggested score threshold. ...
  75. The prediction calculator is generated in a stand-alone spreadsheet, ready to be printed. The layout favors operating the ...