SQL Server 2016

  1. Server returned error code "403 - Forbidden". This error can occur when the specified resource needs "https" access, but ...
  2. Server setting 'Allow triggers to be fired which fire other triggers (nested triggers)' must exist on updatable Subscribers. ...
  3. Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required. ...
  4. Server startup failed due to insufficient memory for descriptor hash tables. Reduce non-essential memory load or increase ...
  5. Server startup failed due to insufficient memory for descriptor. Reduce non-essential memory load or increase system memory. ...
  6. Server TCP provider has stopped listening on port %1!s! due to a CreateSocket failure. Error: %2!s!, state: %3!s!. The server ...
  7. Server TCP provider has stopped listening on port %1!s! due to an AcceptEx failure. Socket error: %2!s!, state: %3!s!. The ...
  8. Server Type is either SQL Server or an OLE DB provider installed on the server. If SQL Server is selected then the Linked ...
  9. Server user '%1!s!' is not a valid user in database '%2!s!'. Add the user account or 'guest' user account into the database ...
  10. Server-level event notifications can not be delivered. Either Service Broker is disabled in msdb, or msdb failed to start. ...
  11. Servername "%1!s!" cannot be empty or null. It can only be made up of lowercase letters 'a'-'z', the numbers 0-9 and the ...
  12. Service account cannot be specified when adding a brick to a matrix. Remove the command prompt parameter {0}, and then rerun ...
  13. Service Account. Press tab to specify a built-in account or windows user account to run the report server service. 2 of 11. ...
  14. Service applications, solutions, event registration, library templates, and service permissions are removed only when the ...
  15. Service Broker could not upgrade conversation session keys in database '%1!s!' to encrypted format (Error: %2!s!). The Service ...
  16. Service Broker could not upgrade conversation with conversation_handle '%1!s!'. Use END CONVERSATION . WITH CLEANUP to delete ...
  17. Service broker dialog '%1!s!' could not be closed because the database with id '%2!s!' is not available. Consider closing ...
  18. Service broker dialog '%1!s!' could not be closed due to a broker error in database with id '%2!s!' because of the following ...
  19. Service broker failed to clean up conversation endpoints on database '%1!s!'. Another problem is preventing SQL Server from ...
  20. Service Broker in database '%1!s!' has a pending conversation upgrade operation. A database master key in the database is ...
  21. Service Broker message delivery is not enabled in this database. Use the ALTER DATABASE statement to enable Service Broker ...
  22. Service Broker needs to access the master key in the database '%1!s!'. Error code:%2!s!. The master key has to exist and ...
  23. Service Broker provides queuing and reliable messaging for the Database Engine. Service Broker uses an endpoint for communication ...
  24. Service Broker received an END CONVERSATION message on this conversation. Service Broker will not transmit the message; it ...
  25. Service Broker received an error message on this conversation. Service Broker will not transmit the message; it will be held ...
  26. Service Broker was unable to allocate memory for cryptographic operations. This message is a symptom of another problem. ...
  27. Service to launch Advanced Analytics Extensions Launchpad process that enables integration with Microsoft R Open using standard ...
  28. Service to launch full-text filter daemon process which will perform document filtering and word breaking for SQL Server ...
  29. Ser[ver server_name Optional. Specifies the name of SQL Server instance from which to retrieve the package. If you omit this ...
  30. Session cannot be created because maximum number of active sessions was already reached. Consumer must release one or more ...
  31. Session Manager: A session footprint was just created or deleted. This is used to trace session footprint creations and deletions. ...
  32. Session mining objects (including special data source views used to process data mining dimensions) cannot be created on ...
  33. Session recovery feature data used in login record to open or recover a connection is structurally or semantically invalid; ...
  34. Session state has been disabled for ASP.NET. The Report Viewer control requires that session state be enabled in local mode. ...
  35. Set compilation debug="true" to insert debugging symbols into the compiled page. Because this affects performance, set this ...
  36. Set partition failed since a different partition already was set in the current transaction. Cross partition operations within ...
  37. Set property_path;value Optional. Overrides the configuration of a variable, property, container, log provider, foreach enumerator, ...
  38. SET STATISTICS XML ON and SET STATISTICS PROFILE ON are not allowed inside any procedure or batch that executes through an ...
  39. Set the reporting options of the package by selecting the events and the information about the running package to report ...
  40. Set the Slice property on partitions with ROLAP storage mode or with proactive caching settings that allow entering ROLAP ...
  41. Set to "True" to enable instant file initialization for SQL Server service. If enabled, Setup will grant Perform Volume Maintenance ...
  42. SetParameterProperties method cannot be called for the specified parameters without first calling SetParameterInfo method. ...
  43. Sets or gets Minimum axis scale region size, in percentage of total axis length, that can be collapsed with the scale break. ...
  44. Sets the maximum number of database objects that can be open at one time on an instance of SQL Server 2000 Database objects ...
  45. Sets with members from multiple levels of a non-parent-child hierarchy cannot be specified as part of a subcube definition. ...
  46. Sets with multiple hierarchies cannot be specified as part of a subcube definition. Use the Crossjoin function or the Crossjoin ...
  47. Sets with multiple members from a level in an unnatural hierarchy cannot be specified as part of a subcube definition. Use ...
  48. Setting @upload_first to 'true' requires the publication to be at publication_compatibility_level of '80RTM' or higher. Use ...
  49. Setting a limit on the number of snapshots stored in history may result in the deletion of snapshots already created. Older ...
  50. Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type ...
  51. Setting DirectQueryMode to any value other than Default is not supported when Analysis Services are not running in Tabular ...
  52. Setting FILESTREAM ON failed on table '%1!s!' because it is not supported operation on system-versioned temporal tables. ...
  53. Setting SYSTEM_VERSIONING to ON failed because column '%1!s!' at ordinal %2!s! in history table '%3!s!' has a different name ...
  54. Setting SYSTEM_VERSIONING to ON failed because column '%1!s!' does not have the same ANSI trimming semantics in tables '%2!s!' ...
  55. Setting SYSTEM_VERSIONING to ON failed because column '%1!s!' does not have the same CLR type in tables '%2!s!' and '%3!s!'. ...
  56. Setting SYSTEM_VERSIONING to ON failed because column '%1!s!' does not have the same collation in tables '%2!s!' and '%3!s!'. ...
  57. Setting SYSTEM_VERSIONING to ON failed because column '%1!s!' does not have the same column set property in tables '%2!s!' ...
  58. Setting SYSTEM_VERSIONING to ON failed because column '%1!s!' does not have the same masking functions in tables '%2!s!' ...
  59. Setting SYSTEM_VERSIONING to ON failed because column '%1!s!' does not have the same nullability attribute in tables '%2!s!' ...
  60. Setting SYSTEM_VERSIONING to ON failed because column '%1!s!' does not have the same sparse storage attribute in tables '%2!s!' ...
  61. Setting SYSTEM_VERSIONING to ON failed because column '%1!s!' does not have the same XML Schema Collection in tables '%2!s!' ...
  62. Setting SYSTEM_VERSIONING to ON failed because column '%1!s!' does not use identical encryption in tables '%2!s!' and '%3!s!'. ...
  63. Setting SYSTEM_VERSIONING to ON failed because column '%1!s!' has data type %2!s! in history table '%3!s!' which is different ...
  64. Setting SYSTEM_VERSIONING to ON failed because column '%1!s!' in history table '%2!s!' corresponds to a generated always ...
  65. Setting SYSTEM_VERSIONING to ON failed because history table '%1!s!' contains invalid records with end of period set before ...
  66. Setting SYSTEM_VERSIONING to ON failed because history table '%1!s!' contains invalid records with end of period set to a ...
  67. Setting SYSTEM_VERSIONING to ON failed because history table '%1!s!' has computed column specification. Consider dropping ...
  68. Setting SYSTEM_VERSIONING to ON failed because history table '%1!s!' has custom unique keys defined. Consider dropping all ...
  69. Setting SYSTEM_VERSIONING to ON failed because history table '%1!s!' has foreign keys defined. Consider dropping all foreign ...
  70. Setting SYSTEM_VERSIONING to ON failed because history table '%1!s!' has IDENTITY column specification. Consider dropping ...
  71. Setting SYSTEM_VERSIONING to ON failed because history table '%1!s!' has ROWGUID column specification. Consider dropping ...
  72. Setting SYSTEM_VERSIONING to ON failed because history table '%1!s!' has table or column constraints defined. Consider dropping ...
  73. Setting SYSTEM_VERSIONING to ON failed because history table '%1!s!' has triggers defined. Consider dropping all triggers ...
  74. Setting SYSTEM_VERSIONING to ON failed because history table '%1!s!' is configured for change data capture. Consider dropping ...
  75. Setting SYSTEM_VERSIONING to ON failed because history table '%1!s!' is not available or it is placed on a read-only file ...