Then what makes you think 108 is appropriate style for the format used in your file?

No it should be CONVERT(datetime, HC_IH_TD_ACTUAL_TIME_TO, 108)

Always read manuals before using tools.

In this case it's BOL ("help" for SQL Server)

Then you need first EXPLICITLY convert to to datetime acording to the format used in the file.

Apparently you convert FROM datetime indtead of converting TO datetime.

What are the datatypes of the columns used in the query?

Don't use CAST for varchar-datetime conversions.

Always use CONVERT with style specified.

Though delimiter "," does its job in most cases it still can fail if someone will try to pass something like this:

Monitor 17","TCO'03" compliant.

For bullet proof solution you need to...

It's not about an offense.

I have not noticed one.

It's about your reasons.

Index gives you desired result using single page reading.

It's theoretically minimal possible amount of reading. Because SQL Server reads...

Join the table to itself on

T1.Descr = T2.Descr AND T1.value = T2.value-1

Did you ever use an index in your life?

For example, an index on a book?

How many pages you need to read to find what is the MIN and MAX keywords...

How many rows, on you opinion, server needs to read to find MAX or MIN value from an index?

Why?

You wanna say it did not work?

If application fails because of special characters in logins then it's programmers who wrote it must be found and eliminated, not the characters.

Those failures mean that application is not protected...

You may use derived tables:

SELECT Three, Three+3 AS Six

FROM (

SELECT 1+2 as Three

) DT

Simple index on DOC_RECEIVED_DATE would allow you to get result from that query in no time.