Table of Contents
SQL Server Error: 106
Severity: 16
Event Logged or not: No
Description:
Too many table names in the query. The maximum allowable is %d.
Severity 16 Description:
Indicates general errors that can be corrected by the user.
Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.
USE master
Go
xp_readerrorlog 0, 1, N'Logging SQL Server messages in file', NULL, NULL, N'asc'
Go
The parameters for XP_READERRRORLOG are:
1. Value of error log file we would like to read. values are 0 = current, 1 = last one before current, 2 = second last before current etc…
2. Log file type:- 1 or NULL = error log, 2 = SQL Agent log
3. Search string 1:- String one you want to search for
4. Search string 2:- String two you want to search for to further refine the results
5. start time for Search
6. end time for search
7. Sort order for search results:- N’asc’ = ascending, N’desc’ = descending
By default, we have 6 Server Error Logs kept but we can increase the number of SQL Server Error Logs from the default value of six.
For other ways to read and find error log location please our artcile https://sqlserver-dba.co.uk/error-log/sql-server-identify-location-of-the-sql-server-error-log-file.html
The table contains error message numbers and the description, which is the text of the error message from the sys.messages catalog view. Where applicable, the error number is a link to further information.
SELECT message_id AS Error, severity AS Severity, [Event Logged] = CASE is_event_logged WHEN 0 THEN 'No' ELSE 'Yes' END, text AS [Description] FROM sys.messages WHERE language_id = 1040 /* replace 1040 with the desired language ID, such as 1033 for US English*/ ORDER BY message_id
Solution was provided by SAP Support for this error on SAP
Reduce Parameter rsdb/max_blocking_factor to 20 and retry.
SQL Server Error: 106
Severity: 16
Event Logged or not: No
Description:
Too many table names in the query. The maximum allowable is %d.
Solution was provided by SAP Support for this error on SAP
Reduce Parameter rsdb/max_blocking_factor to 20 and retry.
I’ve had the same error. It worked for me.
Try a lower value.
Learn about SQL Server detecting logical consistency based issues and how to resolve them.
Learn about SQL Server error 1222 and how to resolve the lock request time out…
Discover the new features of Microsoft SQL Server 2022 and how they compare to previous…
SQL Server Error 1222 lock request time out period exceeded Lock request time out…
SQL Server Error : 427, Severity: 20. Could not load the definition for constraint ID…
SQL Server Error : 204, Severity: 20. Normalization error in node %ls.
This website uses cookies.
I’ve had the same error. It worked for me.
Try a lower value.
SQL Server Error Code and solution summary