In SQL Server, the ANSI_NULLS setting allows you to specify how NULL values are treated in queries.
More specifically, it allows you to specify ISO compliant behaviour of the Equal To (=) and Not Equal To (<>) comparison operators when they are used with NULL values.
SQL Server has an ANSI_NULLS setting that determines how NULL values are evaluated when compared to another value with the Equals (=) and Not Equal To (<>) comparison operators.
While it’s true that you can change the ANSI_NULLS setting at the session level (using SET ANSI_NULLS), each database also has its own ANSI_NULLS setting.
You can check your database to see whether its ANSI_NULLS setting is ON or OFF.
To do this with T-SQL, you can either use the sys.databases catalog view or the DATABASEPROPERTYEX() function.
In SQL Server, you can use the sysmail_help_status_sp stored procedure on the msdb database to check the status of the Database Mail queues.
If you use Database Mail in SQL Server, you can use the sysmail_sentitems view to return a list of all emails that Database Mail has sent.
If you use Database Mail in SQL Server, you can use the sysmail_allitems view to check the status of all emails that Database Mail has processed.
If you’re trying to send email using Database Mail in SQL Server, but it fails to send, you can check the sysmail_event_log view to see why it failed.
The sysmail_event_log view returns one row for each Windows or SQL Server message returned by the Database Mail system. By “message”, I don’t mean the actual mail message. I mean a message such as the error message that explains why the mail failed.
You can also use the sysmail_configure_sp stored procedure to determine what types of messages are logged.
If you’re trying to send mail with SQL Server but it’s not being delivered, try checking the sysmail_faileditems view.
When sending emails from SQL Server, you can check for any unsent mail with the sysmail_unsentitems view.
This is a commonly encountered error in SQL Server when inserting data into a table. The full error goes like this:
Msg 109, Level 15, State 1, Line 1 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.
This happens when you specify more columns in the INSERT statement than the number of values that you’re trying to insert with the VALUES clause.
This will occur if you accidentally omit one or more values from the VALUES clause.
You’d get a similar (but technically different) error if you tried to do the opposite – specify fewer columns in the INSERT statement than you try to insert.
You can use the T-SQL EXCEPT operator in SQL Server to return distinct rows from the left input query that aren’t output by the right input query.