SQL Server 2016
- The following events are available for MyApplication ' 'Startup: Raised when the application starts, before the startup form ...
- The following exception occurred while an operation was being performed on a data source view: %1[%{exception/}%]%[;%{exceptioninner/}%]. ...
- The following exception occurred while the managed IDataReader interface was being used: %1[%{exception/}%]%[;%{exceptioninner/}%]. ...
- The following exception occurred while the managed IDbCommand interface was being used: %1[%{exception/}%]%[;%{exceptioninner/}%]. ...
- The following exception occurred while the managed IDbConnection interface was being used: %1[%{exception/}%]%[;%{exceptioninner/}%]. ...
- The following exception occurred while the SharePoint utility (Microsoft.AnalysisServices.SharePointUtil.dll) was running: ...
- The following exception occurred while the Time Dimension Generator (Microsoft.AnalysisServices.TimeDimGenerator.dll) was ...
- The following existing dimensions were not added to the cube because the wizard could not determine how to use them in a ...
- The following FOR XML features are not supported with WITH XMLNAMESPACES list: EXPLICIT mode, XMLSCHEMA and XMLDATA directives. ...
- The following friendly names are not valid: {0}. A friendly name must be less than 100 characters, must not be a reserved ...
- The following import settings will be used to create a new Integration Services project. Click Import to begin importing ...
- The following information will be used to change credentials. Verify that this information is correct before you continue. ...
- The following information will be used to connect to an existing report server database. Verify this information is correct ...
- The following information will be used to create a new Master Data Services database. Verify that this information is correct ...
- The following information will be used to create a new report server database. Verify this information is correct before ...
- The following information will be used to create the Master Data Services database. Verify that this information is correct ...
- The following is a checklist of incompatibilities that cannot exist in a memory-optimized table. You can find migration assistance ...
- The following is a list of Transact-SQL elements in your stored procedure that are not supported within native compilation. ...
- The following is a list of Transact-SQL elements in your user defined function that are not supported within native compilation. ...
- The following member unique names specified in the attribute permission are no longer valid: {0} Do you wish to remove them? ...
- The following members are from a measure group that is not related to the currency dimension: {0} You can either go back ...
- The following mining model will be deleted from the mining structure: {0} The following mining structure column will be deleted ...
- The following mining structure column will be deleted from the mining structure: {0} Any related mining model columns will ...
- The following mining structure columns will be removed from the '{0}' nested table due to a mining structure key change: ...
- The following objects will be cleared (unprocessed) when the objects selected will be processed. Check the box if you want ...
- The following opened package(s) have references to Package Part {0}, they will be reopened to reflect the change in package ...
- The following partitions or dimension attributes do not contain records, possibly because the filter is too restrictive: ...
- The following peers do not contain the peer information required to set up the topology: {0} The backup file from database ...
- The following products depend on ProductShortName]: 2 If you uninstall ProductShortName], dependent products might not function ...
- The following resources could not be configured during repair without additional user input. Review the warnings to understand ...
- The following services and applications are using files that Setup needs to complete the installation. To avoid a computer ...
- The following setting(s) are not supported by the database you are trying to connect to, therefore these setting(s) will ...
- The following Subscribers cannot replicate their data changes because they are not Registered Subscribers at the Publisher: ...
- The following system error occurred during a call to GetFileSize for file: '%{Note1/}'%1[: %{External/}%]%[, %{External/}%]. ...
- The following system error occurred from a call to GetOverlappedResult for Physical file: '%{PhysicalFile/}', Logical file: ...
- The following table hints are not supported on memory-optimized tables: HOLDLOCK, PAGLOCK, READCOMMITTED, READPAST, READUNCOMMITTED, ...
- The following Transact-SQL error occurred while attempting to execute a statement against the PowerPivot service application ...
- The following transactions must access memory optimized tables and natively compiled modules under snapshot isolation: RepeatableRead ...
- The following users or groups are invalid because they are not from the computer where the virtual directory is being created: ...
- The following warnings were encountered while configuring settings on your SQL Server. These resources / settings were missing ...
- The FOR BROWSE clause is allowed (and ignored) in views when the database compatibility mode is set to 80. The FOR BROWSE ...
- The For Each File enumerator is empty. The For Each File enumerator did not find any files that matched the file pattern, ...
- The FOR XML and FOR JSON clauses are invalid in views, inline functions, derived tables, and subqueries when they contain ...
- The FORCESEEK hint cannot be used with index 0. Correct the index provided to the FORCESEEK hint and resubmit the query. ...
- The FORCE_REGRESSOR parameter for the '%{modelname/}' model is not valid. The '%{strParamName/}' column must be an input ...
- The Forecast tool performs forecasting on a selected table. The forecasted values are added to the original table and highlighted. ...
- The FORECAST_METHOD parameter for the '%{modelname/}' model is not valid. FORECAST_METHOD should be one of the three values ...
- The foreign key '{0}' is not being enforced in the model. An Association or inheritance relationship needs to be created ...
- The foreign key '{0}.{1}.{2}' will not be scripted for article '{3}' because it depends on the unpublished default constraint ...
- The foreign key '{0}.{1}.{2}' will not be scripted for article '{3}' because it references the key constraint '{4}.{5}.{6}' ...
- The foreign key '{0}.{1}.{2}' will not be scripted for article '{3}' because it references the unpublished key constraint ...
- The foreign key '{0}.{1}.{2}' will not be scripted for article '{3}' because it references the unpublished table '{4}.{5}'. ...
- The foreign key '{0}.{1}.{2}' will not be scripted for article '{3}' because one of its referencing columns '{4}' is unpublished. ...
- The foreign key column {0} is used as an input or predictable column in the nested table {1}. This is highly discouraged. ...
- The Form View cannot be displayed because the MDX script has the following syntax error: '{0}' To correct this error, click ...
- The formal parameter "%1!s!" was not declared as an OUTPUT parameter, but the actual parameter passed in requested output. ...
- The formal parameter "{0}" was not declared as an OUTPUT parameter, but the actual parameter passed in requested output. ...
- The format for the date filter is incorrect. Please use a valid SQL Server date or datetime format. For example, valid formats ...
- The format of a message during Web synchronization was invalid. Ensure that replication components are properly configured ...
- The format of supplied parameter sid is invalid. The sid might be incorrect or the sid might describe the wrong type of user. ...
- The format used to define the new variable for Invoke-Sqlcmd cmdlet is invalid. Please use the 'var=value' format for defining ...
- The formatting string. For example, C2 formats numbers as currency with 2 decimal places and N0 formats numbers with no decimal ...
- The forwarded message has been dropped because a transport send error occurred when sending the message. Check previous events ...
- The forwarded message number {0}:{1} on conversation {2}:{3} from service {4} to service {5} was dropped with the following ...
- The fraction of update snapshot transactions that have update conflicts to the total number of update snapshot transactions. ...
- The fractional part of the provided time value overflows the scale of the corresponding SQL Server parameter or column. Increase ...
- The friendly name, "{0}", is not valid. A friendly name must be less than 100 characters, must not be a reserved keyword, ...
- The Full aggregation usage setting should be avoided in cases where an attribute contains a large number of members. If specified ...
- The full path length of the LocalDB instance folder is longer than MAX_PATH. The instance must be stored in folder: %LOC ...
- The full-text catalog '%1!s!' (%2!s!) in database '%3!s!' (%4!s!) will be remounted to recover from a failure. Reason code: ...
- The full-text catalog health monitor reported a failure for full-text catalog '%1!s!' (%2!s!) in database '%3!s!' (%4!s!). ...
- The full-text catalog monitor reported catalog '%1!s!' (%2!s!) in database '%3!s!' (%4!s!) in %5!s! state. This is an informational ...
- The full-text filter component '%1!s!' used to populate catalog '%2!s!' in a previous SQL Server release is not the current ...
- The full-text filter daemon host process has stopped normally. The process will be automatically restarted if necessary. ...
- the full-text for , which in full-text indexing on table ' '. After this change, will no longer participate in the table's ...