Msg 468, Level 16, State 9, Line 3 Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "SQL_Latin1_General_CP1_CS_AS" in the equal to operation.

 Msg 468, Level 16, State 9, Line 3 Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "SQL_Latin1_General_CP1_CS_AS" in the equal to operation error will come when we are not installed MS SQL server with default collation for the instance.

When we install SQL Server, we must select the default collation for the instance. During database creation, we can mention the collation. If ignore, it will default to the instance collation. When we create a character column, you specify the column collation. If not specified, it will default to the database collation. Otherwise it is create a problem when we write queries. To avoid this issue, we can add COLLATE DATABASE_DEFAULT in the join condition. Please refer the below screenshots for your reference. 

Issue:

 

Resolved:

Msg 207, Level 16, State 1, Line 1 Invalid column name in "Dynamic SQL Query" error will come when we are not giving proper single quotes in declaration part. Please find the below issue and resolved screen shot for your reference.

Issue:

Resolved:

Msg 4122, Level 16, State 1, Line 1 Remote table-valued function calls are not allowed.

" Remote table-valued function calls are not allowed " error will come when we execute the query from different server using (Nolock). To resolve this error, Please use "WITH" keyword before (Nolock).

Please find the below screen shot for your reference.

• Issue:

• Resolved:

•