SQL Server 2012

  1. Specify the server and instance name of the report server. The Report Server Web and Windows service accounts for that instance ...
  2. Specify the service account of the report server. This value is required. If you omit this value, Setup will use the default ...
  3. Specify the shared disks to be included in the SQL Server resource cluster group. The first drive will be used as the default ...
  4. Specify the threshold (as a percentage of CPU utilization) for triggering a warning about CPU overload, as measured against ...
  5. Specify the threshold (as a percentage of CPU utilization) for triggering a warning about CPU overload, as measured against ...
  6. Specify the threshold (in days) for triggering a warning about a failure to refresh the data file used by reports in the ...
  7. Specify the threshold for triggering low memory warnings. The default is 5 percent. If available memory falls below this ...
  8. Specify the time in seconds that a query waits for resources before timing out. If the default value of -1 is used, then ...
  9. Specify the uniqueidentifier value in the format xxxxxxxx-xxxx . xxxx, where each x is a hexadecimal digit in the range 0-9 ...
  10. Specify the upper limit of user connections, over which the server is considered to have too many. Exceeding this limit triggers ...
  11. Specify the Windows account of a user that will be automatically granted full access to all models. You can configure only ...
  12. Specify the Windows domain account to be used as the SQL Server Agent proxy account for the utility collection set. Alternatively, ...
  13. Specify this account to enable the use of report data sources that do not require credentials or to connect to remote servers ...
  14. Specify whether SQL Server Setup should discover and include product updates. The valid values are True and False or 1 and ...
  15. Specify whether to filter processes having opened or unopened transactions, or select All to skip filtering using the Open ...
  16. Specifying a password will encrypt certain files that might contain confidential information, but will not encrypt the entire ...
  17. Specifying a semi-colon as a batch separator may cause unexpected results because it is a statement terminator. Do you wish ...
  18. Specifying a semi-colon as a batch separator may cause unexpected results because it is a statement terminator. To continue, ...
  19. Specifying HOLDLOCK as a table hint without parentheses is a deprecated feature and will be removed in the next version of ...
  20. Specifying WITH ROWS in CREATE STATISTICS statements is not supported when you run SQL Server 2008 set to the compatibility ...
  21. SPID %1!s!: transaction rollback in progress. Estimated rollback completion: %2!s!%. Estimated time remaining: %3!s! seconds. ...
  22. SPLIT clause of ALTER PARTITION statement failed because the partition is not empty. Only empty partitions can be split in ...
  23. Split data randomly splits the selected data into two sets, a training set and a testing set, based on a ratio you provide. ...
  24. Split large partitions, with more than {0} million rows or that are over {1} MB in size, into smaller partitions to improve ...
  25. sp_addmergelogsettings failed to add log settings. If log settings already exist for this subscription then use sp_changemergelogsettings ...
  26. sp_addtype cannot be used to define user-defined data types for varchar(max), nvarchar(max) or varbinary(max) data types. ...
  27. sp_cursoropen/sp_cursorprepare: The statement parameter can only be a batch or a stored procedure with a single select, without ...
  28. sp_describe_undeclared_parameters failed to discover parameter metadata for remote procedure call because parameters were ...
  29. sp_indexoption is not supported for XML Index and the table has an XML index on it. Use ALTER INDEX instead to set the option ...
  30. sp_mergecompletecleanup cannot be executed before sp_mergepreparecleanup is executed. Use sp_mergepreparecleanup to initiate ...
  31. sp_mergesubscription_cleanup is used to clean up push subscriptions. Use sp_dropmergepullsubscription to clean up pull or ...
  32. sp_refresh_heterogeneous_publisher was unable to obtain publisher information for Oracle publisher '%1!s!'. sp_refresh_heterogeneous_publisher ...
  33. sp_resetconnection was sent as part of a remote procedure call (RPC) batch, but it was not the last RPC in the batch. This ...
  34. sp_showmemo_xml cannot run when the STATISTICS XML, STATISTICS PROFILE or SHOWPLAN set option is on. Set these options to ...
  35. SQL Azure Federation objects are not supported in {0}. To script the SQL Azure federation objects change the target database ...
  36. SQL Distribution Agent encountered an error. Publisher: %1!s! Publisher Database: %2!s! Publication: %3!s! Subscriber: %4!s! ...
  37. Sql Handle: {0} Statement Start / End Byte Offsets: {1} / {2} The text of the query is not available in the data warehouse. ...
  38. SQL Mail has been removed from this release of SQL Server. Remove all references to SQL Mail functionality, and use Database ...
  39. SQL Mail supports legacy applications that send and receive e-mail messages from the Database Engine. SQL Mail is deprecated ...
  40. SQL Mail supports legacy applications that send and receive e-mail messages from the Database Engine. SQL Mail is deprecated ...
  41. SQL Merge Agent encountered an error. Publisher: %1!s! Publisher Database: %2!s! Publication: %3!s! Subscriber: %4!s! Subscriber ...
  42. SQL Server "Denali" Reporting Services does not support client certificates. Upgrade will continue, but the client certificates ...
  43. SQL Server 2000 Analysis Services (64-bit) was detected as part of a named instance that includes the SQL Server 2000 Database ...
  44. SQL Server 2000 DTS Designer components are required to edit DTS packages. Install the special Web download, "SQL Server ...
  45. SQL Server 2000 instance is not supported by this release of Upgrade Advisor, only SQL2005, SQL2008 or SQL2008 R2 is supported. ...
  46. SQL Server 2005 and later versions add trigger_schema as the last column in the result set returned by the sp_helptrigger ...
  47. SQL Server 2005 and SQL Server 2008 do not allow you to create full-text indexes on nondeterministic and imprecise computed ...
  48. SQL Server 2005 provides a new set of log shipping functions that are incompatible with database maintenance plans. If an ...
  49. SQL Server 2008 R2 Books Online upgrades your existing instance of SQL Server 2008 Books Online on the same machine. Because ...
  50. SQL Server 2012 cannot add any more instances. To continue installing this instance, you must uninstall an existing instance. ...
  51. SQL Server 2012 has introduced new features and has changed existing features to help improve performance, security, and ...
  52. SQL Server 2012 hotfix packages must be installed from the command prompt. To apply this hotfix package, run the following ...
  53. SQL Server 2012 Management Tools cannot be installed because SQL Server 2005 Express Edition with Advanced Services Management ...
  54. SQL Server 2012 Patching usage SetupPatch.exe /Help Displays the correct usage of Setup parameters. /q Setup will not display ...
  55. SQL Server 2012 ScenarioEngine.exe and setuppatch.exe cannot be run in this mode. If you are running ScenarioEngine.exe, ...
  56. SQL Server 2012 Setup is already running and cannot be launched more than once at a time. Complete your current setup action ...
  57. SQL Server 2012 setup requires Microsoft .NET Framework %1!d!.%2!d! ServerCore to be installed. To enable the .NET Framework ...
  58. SQL Server 2012 setup requires Microsoft .NET Framework 4.5 to be installed. For more information about how to install Microsoft ...
  59. SQL Server 2012 software pre-requisites have been installed and require a computer restart. To continue, restart this computer ...
  60. SQL Server 32-bit is not supported on Windows Server Core. Before setup can proceed, you must run the 64-bit version of SQL ...
  61. SQL Server 6.5 saves password hashes in a format that is no longer supported. On systems that were upgraded to SQL Server ...
  62. SQL Server Agent could not access the replication agent. Use the DCOMCNFG utility to confirm that the SQL Server Agent Windows ...
  63. SQL Server Agent does not appear to be running on the destination server. If SQL Server Agent is not running on the destination ...
  64. SQL Server Agent does not support SQL Server Authentication when connecting to SQL Server. Instead, Windows Authentication ...
  65. SQL Server Agent must be configured to use Database Mail in order to send mail. The agent operators list contains only operators ...
  66. SQL Server Analysis Services and SQL Server must be in the same state in order to be upgraded. Both must be either stand-alone ...
  67. SQL Server Assertion: File: , line = %2!s! %3!s!. This error may be timing-related. If the error persists after rerunning ...
  68. SQL Server Assertion: File: , line = %2!s! Failed Assertion = '%3!s!' %4!s!. This error may be timing-related. If the error ...
  69. SQL Server Assertion: File: , line=%2!s! Failed Assertion = '%3!s!'. This error may be timing-related. If the error persists ...
  70. SQL Server Audit failed to access the event log. Make sure that the SQL service account has the required permissions to the ...
  71. SQL Server Audit failed to access the security log. Make sure that the SQL service account has the required permissions to ...
  72. SQL Server Audit failed to create the audit file '%1!s!'. Make sure that the disk is not full and that the SQL service account ...
  73. SQL Server Audit failed to start, and the server is being shut down. To troubleshoot this issue, use the -m flag (Single ...
  74. SQL Server blocked access to %1!s! '%2!s!' of component '%3!s!' because this component is turned off as part of the security ...
  75. SQL Server Books Online is not installed on this computer. To access online Help content, click OK to launch your Web browser ...