If the string you want is always the next-to-last one and is always delimited by '/', this should do it:

SELECT

SUBSTRING(data, LEN(data) - CHARINDEX('/', REVERSE(data), CHARINDEX('/',...

But be careful with BETWEEN, since it is inclusive on both ends.

If you say between Jan 1 and Feb 1 00:00:00.000, attempting to get Jan, you could get some from...

If you don't need the identity column, or any other non-grouped data, I think you can do it all in one step, like so:

...

For performance reasons, you should always avoid manipulating the table columns if at all possible. For example, for the dates, do not do this ever:

... (convert(char(10), email_dt, 121) >=...

FYI, I was talking about a separate table from AuditTypes, basically an AuditTypesControl table.

For maximum flexibility, create another table with:

CheckAuditor, AuditTypeId

Then INNER JOIN to that table to limit what any CheckAuditor can see.

Something like this:

INSERT INTO CheckAuditor (CheckAuditor, AuditTypeId)

SELECT 0, 1 UNION ALL

SELECT...

You can get around the security issue by using sp_altermessage, but that means *every* occurence of the message will be logged.

You might be able to get around that by altering...

Of course the real answer, as always, is "it depends".

If the parameters will match only a single value on the db, it makes sense to use the same plan for...

Only specifying WITH RECOMPILE or equivalent can force a recompile. AFAIK, there is nothing you...

To avoid having to check for a previous WHERE for every condition, you can use the old trick of coding the original statement with:

WHERE 1 = 1

so that all conditions...

And worse off yet is if microsoft were to change the reference date to one that started on anything else other than a monday, you would have to modify your...

Your current date comparisons are faulty. The month and day do not have to exceed the from date for the date to be valid for selection.

For example:

from date =...

Why do you need to limit the note to 255? SQL can obvioulsy handle much more than that.

Is that some type of output restriction?

If so, I would still store...

It's interesting. I thought the requestor was interested in time-of-day across any number of days, rather than just on one 24-hr period.

For example, for the last, say, 2 weeks,...

Also be sure to truncate the @StartTime (of the reporting period) passed in down to the even hour, or you would get a totally incorrect result.