The parameter cannot be NULL when SQL SERVER uses the connection SERVER established by ODBC driver to call the stored procedure. odbcnull

The parameter cannot be NULL when SQL SERVER uses the connection SERVER established by ODBC driver to call the stored procedure. odbcnull

We know that there are a lot of drivers available for SQL SERVER link Server (Linked Server). Recently we found that the link SERVER established by using ODBC's Microsoft OLE DB Driver (Linked Server ), the parameter cannot be NULL when a stored procedure is called.

Otherwise, the following error message is displayed:

The corresponding English error prompt is:

EXEC xxx. xxx. dbo. Usp_Test NULL, NULL, 'all'

Msg 7213, Level 16, State 1, Line 1

The attempt by the provider to pass remote stored procedure parameters to remote server 'xxx' failed. Verify that number of parameters, the order, and the values passed are correct.

The corresponding Chinese error prompt is:

EXEC xxx. xxx. dbo. Usp_Test NULL, NULL, 'all'

Msg 7213, Level 16, State 1, Line 1

An error occurred while the provider passed the remote stored procedure parameters to the remote server 'xxx. Make sure that the number, order, and passed value of the parameter are correct.

EXEC xxx. xxx. dbo. Usp_Test '','', 'all', or assign a proper value to the parameter, no error is reported. In addition, the parameter can be NULL when you call a stored procedure on the Linked Server created using the Microsoft ole db Provider for SQL Server Driver.

The above is a small part of the article that I will share with you all about the content that SQL SERVER cannot set to NULL when calling a stored procedure using the ODBC-driven linked SERVER.

Articles you may be interested in:

• ADO. NET database connection string Summary (Oracle, SqlServer, Access, ODBC)
• Two Methods for connecting to sqlserver2000 in php5.3 (com and ODBC)
• How to configure sqlserver odbc in linux