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