The first time I read the article, I was able to find a way to get the information I needed.
This warning has little effect in a regular scenario, but if you are running SQL with excel, it will prevent you from subsequent operations because of that warning ~ in fact excel executes sql with many limitations and requires more than the odd trick, as I have written before piece . To get back to the point, one way to fix this warning is, of course, to add isnull to all the places in the statement where the aggregate function is used, but it's a pain in the balls if the statement is long and there are many places, so I recommend another, more elegant approach: the
Simply add at the top of the statement.
SET ANSI_WARNINGS OFF;
Get it done.
- EOF -