Check BOL for the GROUPING keyword for more details.

select

RM.fldEditedBy as 'User Login',

case Grouping(RM.fldPriorityCode)

when 0 then RM.fldPriorityCode

else 'Total' end as 'Priority',

count(datediff(day,RM.fldRequestDate,RM.fldComCanDate)) as 'Calls Resolved'

create procedure usp_UpdateTables

    @value varchar(50)

as

BEGIN

UPDATE table1

    SET col1 = @value

UPDATE table2

    SET colA = @value

END

Try using WITH ROLLUP or WITH CUBE.  That along with judicious use of the GROUPING function should produce exactly what you need.

A thorough reading of the BOL entries for the...

The issue here is that since the view is not defined, executing the procedure results in a FATAL error.  Fatal errors cause a procedure to abort processing.  The definition of...

The SQL for storing the results in a table is fairly simple; however, the implementation has some potential pitfalls.

Replace

exec (@sql)  -- How to store the result of this request...

I've been using Spotlight on SQL Server from Quest Software for several months as my main monitoring tool.  It provides some of the drill down capabilities that you are looking...

Thanks for the responses.

By the way, the encryption was NOT my idea....they are vendor supplied procedures which the vendor has encrypted.  (Not that it has stopped me from reading the...

The application is almost entirely sp based.

the use of the Z option in the command line indicates that the command line is encrypted using SQL Server 2000 Encryption.  That is why you cannot find the package...

#1:  For each insert with implicit transactions, the SQL Server engine creates a transaction; with explicit transactions, all inserts are wrapped in a single transaction.  This can best be seen ...