SQL Server 2008 R2

  1. The witness for the mirroring session received error response %1!s! (state %2!s!) from server instance %3!s! for database ...
  2. The witness server instance name must be distinct from both of the server instances that manage the database. The ALTER DATABASE ...
  3. The wizard analyzes the data source view and suggests a cube definition. If you want to build the cube manually, disable ...
  4. The wizard cannot continue because no dimension whose Type property is set to Time is related to the exchange rate measure ...
  5. The wizard cannot find an attribute in the {0} dimension whose Usage property is set to Parent. Before defining a unary operator, ...
  6. The wizard could not create relationships between any existing dimensions and the following measure groups: {0}. You should ...
  7. The wizard could not set the account types. You can set the account types manually after the wizard is finished by right-clicking ...
  8. The wizard detected that changes were made directly to the database using a method other than upgrading the DAC. These changes ...
  9. The wizard extracts the contents of the chosen database and creates an Analysis Services project based on the extracted data. ...
  10. The wizard has detected an account dimension that contains semiadditive members. The server will aggregate members of this ...
  11. The wizard has detected an account dimension, {0}, that contains semiadditive members. The server will aggregate members ...
  12. The wizard has detected an existing currency conversion script in the cube. You can choose to either overwrite the existing ...
  13. The wizard has detected the '{0}' account dimension, which contains semiadditive members. The server will aggregate members ...
  14. The wizard was either unable to find a dimension of type Accounts or the account dimension does not contain an AccountType ...
  15. The wizard will create an attribute for most columns in the dimension tables and attempt to build hierarchies that have multiple ...
  16. The wizard will deploy {0} to the following Analysis Server and database. If the database does not exist, it will be created ...
  17. The wizard will split your data in the mining structure into a training set and a testing set. By default, the data mining ...
  18. The WMI configuration on the specified instance of SQL Server was not validated because the {0} job required for validation ...
  19. The word breakers and filters were significantly changed in SQL Server 2005. In SQL Server 2008, additional improvements ...
  20. The workbook cannot be saved because the size of the PowerPivot data exceeds the 4GB limit allowed by PowerPivot for Excel. ...
  21. The Writeable property of variable, {0}, is set to true. SQL Server 2008 Reporting Services does not support variables that ...
  22. The writeback operation cannot be performed because the cartridge for the data source does not support the LinkChildrenToParent ...
  23. The writeback table format has changed, a new '{1}' table will be used instead of '{0}'. Any data will need to be transferred. ...
  24. The WRITETEXT statement is not allowed because the column is being replicated with Data Transformation Services (DTS) or ...
  25. The WritingMode value 'Rotate270' is not supported in SQL Server 2008 Reporting Services. Set the WritingMode to either 'Horizontal' ...
  26. The XactID and XactSeqno values for the last set of changes committed to the distribution database do not match expected ...
  27. The XML content that is supplied for the sparse column set '%1!s!' contains duplicate references to the column '%2!s!'. A ...
  28. The XML data type method on a remote column used in this query can not be executed either locally or remotely. Please rewrite ...
  29. The Xml index '{0}.{1}.{2}' will not be scripted for article '{3}' because the clustered primary key of the base table will ...
  30. The xml index '{0}.{1}.{2}' will not be scripted for article '{3}' because the clustered primary key of the base table will ...
  31. The xml index '{0}.{1}.{2}' will not be scripted for article '{3}' because the xml columns of the base table are replicated ...
  32. The XML node returned by the XPath query '{0}' on the XML document at the root path '{1}' in the data store is neither an ...
  33. The XML page cannot be displayed Cannot view XML input using %3 style sheet. Please correct the error and then click the ...
  34. The xml schema collection for return parameter of module '%1!s!' has been altered while the batch was being executed. Please ...
  35. The xml schema collection for variable '%1!s!' has been altered while the batch was being executed. Remove all XML schema ...
  36. The XML schema data type information for "%1!s!" on element "%2!s!" has changed. Please re-initialize the metadata for this ...
  37. The XML script engine does not support script fragments. This error was probably caused by having a script tag with the language ...
  38. The XML Source Adapter was unable to process the XML data. An inline schema must be the first child node in the source Xml. ...
  39. The XML Source Adapter was unable to process the XML data. No inline schema was found in the source XML, but the "UseInlineSchema" ...
  40. The XML Source Adapter was unable to process the XML data. The content of an element can not contain a reference (ref) to ...
  41. The Xml source document contains the "xsi:nil" attribute with a value of true on the "{0}" element, therefore the element ...
  42. The Xml source document contains the fixed value for "{0}" of "{1}" which is not consistent with the value of "{2}" provided. ...
  43. The XP callback function '%1!s!' failed in extended procedure '%2!s!' because it was executed within an INSERT-EXEC statement ...
  44. The XP callback function '%1!s!' failed in extended procedure '%2!s!' because the extended procedure is called inside an ...
  45. The xp_cmdshell extended stored procedure runs operating system commands from within the Database Engine. Enable xp_cmdshell ...
  46. The xp_cmdshell extended stored procedure runs operating system commands from within the Database Engine. Enable xp_cmdshell ...
  47. The xp_cmdshell proxy account information cannot be retrieved or is invalid. Verify that the '%1!s!' credential exists and ...
  48. The XSLT path is invalid. It refers to an external resource, uses invalid syntax, or the XSLT was not found in the catalog ...
  49. The {0} '{1}' contains a set of TablixMembers with FixedData set to true in the TablixColumnHierarchy which is incompatible ...
  50. The {0} '{1}' contains an invalid {2} (Expected: {3}; Actual {4}). The {2} of inner or nested DataRegions must be the same ...
  51. The {0} '{1}' contains an invalid {2} Name, '{3}'. The name must be greater than 0 and less than or equal to {4} characters. ...
  52. The {0} '{1}' contains an invalid {2}. There is a {3} with an invalid {4} at level {5}. If there is a {3} with a {4} in this ...
  53. The {0} '{1}' has an inconsistent number of {2}Cells within the {2}Row. Each {2}Row must have the same number of {2}Cells. ...
  54. The {0} '{1}' has an incorrect number of TablixCells. The number of TablixCells in a TablixRow must equal the number of innermost ...
  55. The {0} '{1}' has an incorrect number of TablixRows. The number of TablixRows must equal the number of innermost TablixMembers ...
  56. The {0} '{1}' has an incorrectly set {2} properties within the {3}. All TablixMembers with FixedData set to true must be ...
  57. The {0} '{1}' has an incorrectly set {2} property within the {3}. Only the outermost TablixMembers in a hierarchy can have ...
  58. The {0} '{1}' has an incorrectly set {2} property. {2} is not allowed to be set on row TablixMember, unless it is also set ...
  59. The {0} '{1}' has an incorrectly set {2} property. {2} is not allowed to be set on the first column TablixMember when Tablix.GroupBeforeRowHeaders ...
  60. The {0} '{1}' has an invalid set of TablixCells. The combined value of the ColSpan properties of the TablixCells within a ...
  61. The {0} '{1}' has an invalid TablixCell. The {2} of the TablixCell is invalid. The TablixCell cannot span columns under TablixMembers ...
  62. The {0} '{1}' has an invalid TablixHeader. The {2} of the TablixHeader is invalid. The TablixHeader can only span one column. ...
  63. The {0} '{1}' has an invalid TablixHeader. The {2} of the TablixHeader is invalid. The TablixHeader can only span one row. ...
  64. The {0} '{1}' has an invalid TablixMember. The child TablixMember with Group name '{2}' is not a dynamic TablixMember and ...
  65. The {0} '{1}' has an invalid {2}. A {2} that is dynamic (i.e., has a Group specified) or has dynamic descendants must have ...
  66. The {0} '{1}' has an invalid {2}. The CellContents for this {2} must be omitted because it is covered by a span from another ...
  67. The {0} '{1}' has an invalid {2}. The {2} has an invalid {3}, '{4}'. Child {2} elements of Static {2} elements must be Dynamic ...
  68. The {0} '{1}' has an invalid {2}. The {2} has an invalid {3}, '{4}'. Non-Static {3} elements must contain at least 1 {5}. ...
  69. The {0} '{1}' has an invalid {2}. The {2} must have the same value set for the {3} property as those following or preceding ...
  70. The {0} '{1}' has an {2} with an invalid {3}. The {3} can be an integer between -90 an 90, inclusive, or the values 'RightAngle' ...
  71. The {0} '{1}' is bound to a data source using the {2} data extension. The data extension returned an invalid database collation ...
  72. The {0} '{1}' was created, but an error occurred setting permissions. Use the object properties dialog to set permissions ...
  73. The {0} algorithm cannot be used, because it requires a KEY TIME column, which is not present in the {1} structure. Select ...
  74. The {0} contains a Function "{1}" which takes Argument "{2}" with data type Float but the value supplied has data type Decimal. ...
  75. The {0} contains a Function "{1}" with a literal set for Argument "{2}". This argument cannot take a literal set as a value. ...