SQL Server 2016
- The SQLServerAgent mail session is not running; check the mail profile and/or the SQLServerAgent service startup account ...
- The SSIS Data Flow Task could not be created. Verify that DTSPipeline.dll is available and registered. The wizard cannot ...
- The SSIS logging infrastructure failed with error code 1!8.8X!. This error indicates that this logging error is not attributable ...
- The SSIS logging provider "%1!s!" failed with error code 2!8.8X! (%3!s!). This indicates a logging error attributable to ...
- The SSIS managed helper object failed during creation with error 1!8.8X! "%2!s!". This occurs whenever CoCreateInstance CLSID_DTSManagedHelper ...
- The SSIS Package Upgrade Wizard upgrades packages created using previous versions of SQL Server tools and object models to ...
- The SSIS Runtime has failed to start the distributed transaction due to error 1!8.8X! "%2!s!". The DTC transaction failed ...
- The SSIS Runtime object could not be created. Verify that DTS.dll is available and registered. The wizard cannot continue ...
- The SSISDB in the specified instance {0} is in an AlwaysOn availability group. Before you can disable SSIS support for AlwaysOn ...
- The SSRS service application is not mapped to this web application. Use the SSRS service application pages to associate the ...
- The SSRSSharePointModeCheck command line parameter is not supported for this Setup action or scenario. The SSRSSharePointModeCheckparameter ...
- The stage of processing when the event is raised. The event can be raised either when the DML plan is compiled or when it ...
- The stage of processing when the event is raised. The event can be raised either when the query plan is compiled or when ...
- The start index %1!d! is not valid for function "%2!s!". The start index value must be an integer greater than 0. Start index ...
- The start index was not valid for function SUBSTRING. The start index value must be an integer greater than zero. The start ...
- The start width of the range. Measured as a percentage of the size of the gauge (height for horizontal gauges, width for ...
- The StartMode property indicates the start mode of the Win32 base service. \"Boot\" specifies a device driver started by ...
- The StartName property indicates the account name under which the service runs. Depending on the service type, the account ...
- The StartService method attempts to place the service into its startup state. It returns one of the following integer values: ...
- The startup parameter -h (Hot Add memory metadata with AWE on a 32-bit server) is enabled on the instance of SQL Server. ...
- The state indicator, {0}, was detected in the report. SQL Server 2008 Reporting Services does not support state indicators. ...
- The state indicator, {0}, was removed from the report. SQL Server 2008 Reporting Services does not support state indicators. ...
- The state of the local availability replica in availability group '%1!s!' has changed from '%2!s!' to '%3!s!'. %4!s!. For ...
- The state of your SQL Server installation was not changed after the setup execution. Please review the summary.txt logs for ...
- The statement %1!s! is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ...
- The statement failed because a clustered columnstore index cannot be created on a table enabled for %1!s!. Consider disabling ...
- The statement failed because a clustered columnstore index cannot be created on a table that has a nonclustered index. Consider ...
- The statement failed because a columnstore index cannot be a filtered index. Consider creating a columnstore index without ...
- The statement failed because a columnstore index cannot be created in this edition of SQL Server. See Books Online for more ...
- The statement failed because a columnstore index cannot be created on a column set. Consider creating a nonclustered columnstore ...
- The statement failed because a columnstore index cannot be created on a column with filestream data. Consider creating a ...
- The statement failed because a columnstore index cannot be created on a sparse column. Consider creating a nonclustered columnstore ...
- The statement failed because a columnstore index cannot be created on a view. Consider creating a columnstore index on the ...
- The statement failed because a columnstore index cannot be unique. Create the columnstore index without the UNIQUE keyword ...
- The statement failed because a columnstore index cannot have included columns. Create the columnstore index on the desired ...
- The statement failed because a columnstore index must be partition-aligned with the base table. Create the columnstore index ...
- The statement failed because a columnstore index on a partitioned table must be partition-aligned with the base table. Consider ...
- The statement failed because a nonclustered columnstore index cannot be reorganized. Reorganization of a nonclustered columnstore ...
- The statement failed because a nonclustered index and the underlying clustered columnstore index must be partition-aligned. ...
- The statement failed because a nonclustered index cannot be created on a table that has a clustered columnstore index. Consider ...
- The statement failed because a secondary dictionary reached the maximum size limit. Consider dropping the columnstore index, ...
- The statement failed because a table with a clustered columnstore index cannot have triggers. Consider removing all triggers ...
- The statement failed because adding an identity column with other columns with default not null is not supported for columnstore ...
- The statement failed because column '%1!s!' (ID=%2!s!) uses collation %3!s!, which is not recognized by older client drivers. ...
- The statement failed because column '%1!s!' on table '%2!s!' is a computed column. Columnstore index cannot include a computed ...
- The statement failed because columnstore indexes are not allowed on table types and table variables. Remove the column store ...
- The statement failed because specifying %1!s! is not allowed when creating a columnstore index. Consider creating a columnstore ...
- The statement failed because specifying %1!s! is not allowed when creating a rowstore index. Consider creating a rowstore ...
- The statement failed because specifying a key list is not allowed when creating a clustered columnstore index. Create the ...
- The statement failed because specifying FILESTREAM_ON is not allowed when creating a columnstore index. Consider creating ...
- The statement failed because specifying key list is missing when creating an index. Create the index with specifying key ...
- The statement failed because specifying ORDER is not a valid option for index creation. Consider creating an index without ...
- The statement failed because specifying ORDER is not a valid option for non-clustered columnstore index creation. Consider ...
- The statement failed because specifying sort order (ASC or DESC) is not allowed when creating a columnstore index. Create ...
- The statement failed because specifying SORT_IN_TEMPDB is not allowed when creating a columnstore index without ORDER. Consider ...
- The statement failed because table '%1!s!' uses vardecimal storage format. A columnstore index cannot be created on a table ...
- The statement failed because the %1!s! option is not allowed when creating a columnstore index. Create the columnstore index ...
- The statement failed because the definition of a column belonging to clustered columnstore index cannot be changed. Consider ...
- The statement failed because the sql_variant value uses collation %1!s!, which is not recognized by older client drivers. ...
- The statement failed. A columnstore index cannot include a decimal or numeric data type with a precision greater than 18. ...
- The statement failed. Column '%1!s!' has a data type that cannot participate in a columnstore index. Omit column '%2!s!'. ...
- The statement failed. Column '%1!s!' is either a primary key or a partitioning key that must be included, but a columnstore ...
- The statement is not supported on this version of the operating system. Could not find function entry point '%1!s!' in Httpapi.dll. ...
- The statement, INSERT INTO . '%s{name/}'.CASES, is not valid when used with a mining model. This statement can be used only ...
- The status of association {0} could not be changed, because the current association status is incorrect. In order for the ...
- The status of the collector cannot be null. This may indicate an internal corruption in the collector configuration data. ...
- The status of the schema change could not be updated because the publication compatibility level is less than 90. Use sp_changemergepublication ...
- The STOPAT clause provided with this RESTORE statement indicates that the tail of the log contains changes that must be backed ...
- The STOPAT clause specifies a point too early to allow this backup set to be restored. Choose a different stop point or use ...
- The STOPAT option cannot be used with this partial restore sequence because one or more FILESTREAM filegroups are not included. ...
- The stoplist '%1!s!' already contains full-text stopword '%2!s!' with locale ID %3!s!. Specify a unique stopword and locale ...
- The stoplist '%1!s!' does not contain fulltext stopword '%2!s!' with locale ID %3!s!. Specify a valid stopword and locale ...
- The STOPPING_TOLERANCE parameter for the '%{modelname/}' model is not valid. STOPPING_TOLERANCE must be integer and greater ...
- The StopService method places the service in the stopped state. It returns an integer value of 0 if the service was successfully ...
- The Storage Map can be looked up only from the type in conceptual model. It cannot be looked up from type in the following ...