SQL Server 2012

  1. Opening MY certificate store failed with error "%1!s!".This occurs in CPackage::LoadUserCertificateByName and CPackage::LoadUserCertificateByHash. ...
  2. Opening registry key '{0}' in view '{1}' with access '{2}' in order to set an access control entry to configure the SQL Server ...
  3. Opening the embedded file '{0}' containing the access control entries to apply in order to configure the SQL Server Browser ...
  4. Opening the file "%1!s!" for writing failed because the disk is full. There is not sufficient disk space to save this file. ...
  5. Opening the file "%1!s!" for writing failed. The file exists and cannot be overwritten. If the AllowAppend property is FALSE ...
  6. Opening this file in the Tabular Model Designer causes a script to be executed on an Analysis Services server. Do not open ...
  7. OPENINGPERIOD=1=[ Level , Member ]=Returns the first sibling among the descendants of a specified level, optionally at a ...
  8. OPENXML encountered a problem identifying the metaproperty namespace prefix. Consider removing the namespace parameter from ...
  9. OPENXML requires a metaproperty namespace to be declared if 'mp' is used for another namespace in sp_xml_preparedocument. ...
  10. Operation '%1!s!' on a database '%2!s!' (Database ID: %3!s!) in availability group '%4!s!' failed with SQL Server error %5!s! ...
  11. Operation cannot be completed, because the current user does not have sufficient permissions on the instance of SQL Server. ...
  12. Operation cannot be completed, because the current user does not have sufficient permissions on the instance of SQL Server. ...
  13. Operation failed. The index entry of length %1!s! bytes for the index '%2!s!' exceeds the maximum length of %3!s! bytes. ...
  14. Operation not allowed because of pending cleanup of online index build. Wait for cleanup to complete and re-run the operation. ...
  15. Operation on the availability group '%1!s!' has been cancelled or terminated, either because of a connection timeout or cancellation ...
  16. Operation on the local availability replica of availability group '%1!s!' failed. The local copy of the availability group ...
  17. Operator node identifier. Use this value to locate the operator in the XML query plan/graphical plan using the NodeId attribute. ...
  18. Optimization settings cannot be applied to Partition {0} in MeasureGroup {1} in Cube {2} because it is not present in the ...
  19. Optional: Enter the default target server URL to host new reports. For example: http:// /reportserver for a report server ...
  20. Oracle functions can be converted into SQL Server functions only if some requirements are met, and sometimes exception processing ...
  21. Oracle OCI client library '%1' could not be found. Verify that either the environment variable ORACLE_HOME is set or that ...
  22. Oracle Publisher '{0}' contains no objects that can be replicated. The most common reason for this is missing permissions. ...
  23. Oracle Publisher '{0}' contains no objects that can be replicated. The most common reasons for this are missing permissions ...
  24. Oracle server instance '{0}' has been previously configured to use '{1}' as its Distributor. To begin using '{2}' as its ...
  25. Oracle Snapshot Begin = Source Owner: {0} Source Table: {1} Publication: {2} Article: {3} Working Directory: {4} Schema Script: ...
  26. Oracle treats empty strings (') as nulls. For the same behavior in SQL Server, you should use isnull(expr,') in string concatenations. ...
  27. ORDER=1= Set , { String Expression | Numeric Expression }[, ASC | DESC | BASC | BDESC]=Arranges the members of a specified ...
  28. Ordering specifies the sequence to use for displaying the members of an attribute. By default, attributes are ordered by ...
  29. Orphan Cleanup is not due to be run on this database at this time. Orphan Cleanup only to be run once per orphan_scan_period. ...
  30. Out of line bindings cannot use the implicit datasource '.'. Use an explicit DataSource ID in the bindings specified for ...
  31. Out of sequence before or after elements are not permitted inside a single sync block. If there is more than one of these, ...
  32. Output column "%1!s!" (%2!d!) is mapped to a Pivoted Value input column, but its PivotKeyValue property value is missing. ...
  33. Output column "%1!s!" (%2!d!) references input column with lineage ID %3!d!, but no input could be found with that lineage ...
  34. OutputEventType' property cannot be accessed because the adapter is in the process of constructing. Wait until the adapter ...
  35. Overrides the current thread's CurrentUICulture property for all ' resource lookups using this strongly typed resource class. ...
  36. Overrides the current thread's CurrentUICulture property for all resource lookups using this strongly typed resource class. ...
  37. Oversampling creates a data set that contains a specific ratio of a selected data item. For example, it can be used to guarantee ...
  38. Overwriting existing file '%{filename/}' while saving embedded PowerPivot data for dimension '%{dimname/}'. Save Mask=' {msksave/}'][Data ...
  39. P Password for the specified SQL server user when the authentication mode is sql, not required to be specified when authentication ...
  40. Package configurations enable the properties of package objects to be dynamically updated at run time. The configurations ...
  41. Package deployment was successful with warnings. Check the system log for further details and instructions on how to correct. ...
  42. Package execution completed with error. Click here to switch to design mode, or select Stop Debugging from the Debug menu. ...
  43. Package execution completed with success. Click here to switch to design mode, or select Stop Debugging from the Debug menu. ...
  44. Package execution on IS Server failed. Execution ID: %1!I64d!, Execution Status:%2!d!. To view the details for the execution, ...
  45. Package: {0} {1} is an invalid SQL Server update from. This update will be skipped as the expected property '{2}' is not ...
  46. Package: {0} {1} is an invalid SQL Server update. This update will be skipped as it is not applicable for this setup architecture. ...
  47. Package: {0} {1} is an invalid SQL Server update. This update will be skipped as its language '{2}' is not applicable for ...
  48. Package: {0} {1} is an invalid SQL Server update. This update will be skipped as the expected property '{2}' is missing. ...
  49. Package: {0} {1} is an invalid SQL Server update. This update will be skipped as the expected property '{2}' is not a valid ...
  50. Package: {0} {1} is an invalid SQL Server update. This update will be skipped as the expected property '{2}' is not a valid ...
  51. PACKAGEPATH attribute is empty in the XML node "{0}". The package file may be corrupt. The offending ForEachPropertyMapping ...
  52. Pack[age package name Optional. Use this option to specify the package to be used in an execution. It is supposed to be used ...
  53. Page %1!s! cannot be restored from this backup set. RESTORE PAGE can only be used from full backup sets or from the first ...
  54. Page %1!s! in database ID %2!s! is allocated in the SGAM %3!s! and PFS %4!s!, but was not allocated in any IAM. PFS flags ...
  55. Page %1!s! in database ID %2!s! is allocated to both object ID %3!s!, index ID %4!s!, partition ID %5!s!, alloc unit ID %6!s! ...
  56. Page %1!s! is a control page which cannot be restored in isolation. To repair this page, the entire file must be restored. ...
  57. Page %1!s!, slot %2!s! in object ID %3!s!, index ID %4!s!, partition ID %5!s!, alloc unit ID %6!s! (type "%7!s!"). Column ...
  58. Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID %1!s! pages from %2!s! to %3!s!. ...
  59. PARALLELPERIOD=1=[ Level , Numeric Expression , Member ]=Returns a member from a prior period in the same relative position ...
  60. Parameter "%1!s!" is for non-SQL Server Publishers only. The value of this parameter must be "%2!s!" for a SQL Server Publisher. ...
  61. Parameter "%1!s!": Function or procedure parameters with improperly formatted or deprecated names are not supported through ...
  62. Parameter "%1!s!": If the %2!s! attribute appears on a parameter value node of type "%3!s!" (in the namespace "%4!s!"), it ...
  63. Parameter "{0}" is configured to receive a value from an environment variable named "{2}" but there is no environment variable ...
  64. Parameter "{0}" is configured to receive a value from an environment variable named "{2}", but there is no environment variable ...
  65. Parameter "{0}" is configured to receive a value from an environment variable named "{2}", but there is no environment variable ...
  66. Parameter '%1!s!': Incompatible XML attributes were present. The '%2!s!' attribute and the '%3!s!' attribute may not both ...
  67. Parameter '%1' cannot be longer than %2!d! characters. Shorten the value specified for this parameter and restart the replication ...
  68. Parameter '@add_to_active_directory' cannot be set to TRUE because Active Directory client package is not installed properly ...
  69. Parameter '{0}' has inconsistent data types in its value array. Change the values in the array to have the same data type. ...
  70. Parameter '{0}': XmlSchemaCollectionDatabase or XmlSchemaCollectionOwningSchema is non-empty, but XmlSchemaCollectionName ...
  71. Parameter @attach_query_result_as_file cannot be 1 (true) when no value is specified for parameter @query. A query must be ...
  72. Parameter @role_name cannot be empty. Specify a value for @role_name and retry the operation. Supply null as the value if ...
  73. Parameter @sensitivity does not support the value "%1!s!". Mail sensitivity must be one of NORMAL, PERSONAL, PRIVATE, or ...
  74. Parameter Data Generation Options screen Configuration tab Testable objects Lists subprograms and their arguments. By default, ...
  75. Parameter Information cannot be derived from SQL statements with sub-select queries. Set parameter information before preparing ...