If you get error Msg 15281, Level 16 in SQL Server, chances are you’re trying to run an ad hoc distributed query, but you haven’t enabled ad hoc distributed queries.
This can be fixed easily by enabling ad hoc distributed queries.
errors
How to Fix: “SQLServerAgent is not currently running…”
If you’ve created a SQL Server Agent job, and you’re now trying to test it to see if it will run properly, you may encounter an ugly error message that reads, among other things, “SQLServerAgent is not currently running so it cannot be notified of this action”.
Fortunately, this is easy to fix.
SQL Server Error 206: Operand type clash
SQL Server error Msg 206, Level 16 is a common error to get when inserting data into a table.
It happens when you’re trying to insert data into a column that is incompatible with the data type you’re trying to insert.
This could happen if you accidentally try to insert data into the wrong column (or even the wrong table). But it could also happen if you incorrectly assume that SQL Server will convert the data for you.
To fix this issue, make sure you’re inserting the correct data type.
How to Fix “Conversion failed when converting the value to data type” in SQL Server
SQL Server error Msg 245, Level 16 tells us that there was a problem when trying to convert a value to a specific data type.
You’ll get this error if you try to insert the wrong data type into a column.
To fix this issue, make sure the data type of the value you’re trying to insert, matches the column’s type.
How to Fix “The select list for the INSERT statement contains fewer items than the insert list”
SQL Server error 120 occurs when you don’t specify enough columns in your INSERT list when using a SELECT list for the values to insert.
To be more specific, it happens when you use a SELECT list in your INSERT statement, but the SELECT list doesn’t return as many columns as you’re specifying with the INSERT.
This is easy to fix. Simply make sure the number of columns match between your INSERT and SELECT list.
How to Fix “ALTER TABLE SWITCH statement failed”
If you’re getting error 4939 while trying to switch a partition in SQL Server, it’s probably because you’re trying to switch to a partition that uses a different filegroup.
One of the requirements of switching partitions is that both the source table or partition, and the target table or partition, must be located in the same filegroup.
How to Fix “Only one expression can be specified in the select list…” in SQL Server
In SQL Server, error message 116 occurs when you try to select multiple columns in a subquery without introducing it with the EXISTS operator.
How to Fix “The partition scheme ‘…’ does not have any next used filegroup” in SQL Server
You’ll get error 7710 if you try to split a partition in SQL Server, but you haven’t specified a “next used” filegroup.
How to Fix “ALTER TABLE SWITCH statement failed” Msg 4982 (SQL Server)
If you get error message 4982 in SQL Server, it’s because your source table doesn’t have a constraint that restricts data to only the range supported by the partition that you’re trying to switch to.
SQL Server Error 113: Missing end comment mark ‘*/’
SQL Server error message 113 occurs when you omit a closing comment mark.
This can occur when you open a comment but forget to close it. It can also occur when you accidentally type an opening comment.
There may also be odd occasions where you get this error due to other factors, such as the way your SQL utility handles certain keywords etc.