Home » understanding sql error messages

understanding sql error messages

SQL Server Error : 109, Severity: 15. There are more columns in the INSERT statement

SQL Server Error : 109 Details

SQL Server Error: 109 Severity: 15 Event Logged or not: No Description: There are more columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement. Severity 15 Description: Indicates syntax errors in the Transact-SQL command.

 

Cause for the Error

This issue happens when the number of values supplied in the VALUES clause is less than the number of columns specified in an INSERT to a table using the INSERT INTO… VALUES format, as described in the error message.

The following INSERT statement, for example, will result in … Read the rest

SQL Server Error : 110, Severity: 15. There are fewer columns in the INSERT st

SQL Server Error : 110 Details

SQL Server Error: 110 Severity: 15 Event Logged or not: No Description: There are fewer columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement. Severity 15 Description: Indicates syntax errors in the Transact-SQL command.

Reading sql server error log location from SQL Query

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 Read the rest

SQL Server Error : 111, Severity: 15. ‘%ls’ must be the first statement in a q

SQL Server Error : 111 Details

SQL Server Error: 111 Severity: 15 Event Logged or not: No Description: ‘%ls’ must be the first statement in a query batch. Severity 15 Description: Indicates syntax errors in the Transact-SQL command.

 

Cause for Resolving the Error

Example below of some code that would cause this error:
DROP VIEW IF EXISTS vOne;

CREATE VIEW vOne AS
SELECT * FROM table1;

Msg 111, Level 15, State 1, Line 3
‘CREATE VIEW’ must be the first statement in a query batch.

Above, we are executing two statements: a DROP VIEW and a CREATE VIEW.

The CREATE VIEW command cannot be coupled with other statements in the same batch, according to T-SQL batch restrictions.

In other … Read the rest

SQL Server Error : 107, Severity: 15. The column prefix ‘%.*ls’ does not match

SQL Server Error : 107 Details

SQL Server Error: 107 Severity: 15 Event Logged or not: No Description: The column prefix ‘%.*ls’ does not match with a table name or alias name used in the query. Severity 15 Description: Indicates syntax errors in the Transact-SQL command.

Reading sql server error log location from SQL Query

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 … Read the rest