Just wondering, who is putting you up to something like this? I can see this going sideways very fast. Without understanding what you're really trying to achieve, I'm hesitant...

could you post the structure of the table and some sample data? Should be fairly easy. You might have to do a summary query to do the counts and then...

Use a TRY/CATCH block and return the message in the CATCH block?

Here's another option... use the OUTPUT clause to insert some/all of the records inserted in your stored procedure to another table:

http://www.databasejournal.com/features/mssql/tsql-understanding-how-to-use-the-insert-statement-to-populate-your-database-tables.html

Basically imitates a trigger without all the nasty side effects.

How are you doing the insert into the first table? Is it a bulk insert or one at a time? You might be able to create a variable...

Did you look in the Articles section for Calendar tables?

Todd Fifield's articles

http://www.sqlservercentral.com/articles/70482/%5B/url%5D

http://www.sqlservercentral.com/articles/T-SQL/70743/%5B/url%5D

http://www.sqlservercentral.com/articles/T-SQL/72345/%5B/url%5D

Then you'd just add your rule(s) to the Calendar table so that you could roll up your data any...

Might just be me, but I'm not entirely sure I'm following. Could you please post some sample data and the expected solution? Are you allowed to write stored...

Wouldn't you use Integration Services for that?

Create a package that does what you want, and then create a schedule for it.

You could try using BCP OUT with a format file...

https://www.simple-talk.com/sql/database-administration/working-with-the-bcp-command-line-utility/

Why not

=IIf(Fields!GrandTotalBillableRatio.Value >= 2.0, "Green",

, IIf(Fields!GrandTotalBillableRatio.Value >= 1.75, "Yellow",

, IIf(Fields!GrandTotalBillableRatio.Value >= 0, "Red", "Silver")))

write a stored procedure to insert the results of the DMV into a table in your database and then call it from the command line?

Are you reporting against a live database or a read-only copy?

Huh? This has nothing to do with the problem.

execute a select statement with the same filter to make sure you don't get any false positives, and when you've fixed that part, use the filter/where clause in your update...

It should. It will update every record that would be selected by the filter, though. So you may update more records than you intended to.