See if this works:

CREATE TABLE #temp

(

guidchar(5),

statuschar(3),

INOUT_timedatetime

)

insert into #temp

SELECT '1djey', 'OUT', '05/22/2014 17:13:00'

UNION

SELECT '1djey', 'IN', '05/22/2014 05:00:00'

UNION

SELECT '1djey', 'OUT', '05/22/2014 4:13:00'

UNION

SELECT '1djey', 'IN', '05/22/2014 2:00:00'

UNION

SELECT '4heyk', 'OUT', '05/22/2014 18:10:00'

UNION

SELECT '4heyk', 'IN',...

Well done Luis, I haven't had the opportunity to use the Cross Join, but I will remember it for any future needs. With not knowing about the cross join...

thomashohner (5/9/2014)

---

I saw mounts on Newegg for triple monitor setup. As interesting as that sounds I think I am in concurrence with everyone about the duals. I know I could...

Steve Jones - SSC Editor (5/7/2014)

---

Jack Corbett (5/7/2014)

---

Good editorial today. I want 3 things from a manager:

1. Direction - I don't always want to be picking...

Steph Locke (5/7/2014)

---

Hopefully someone can assist with the relevant citation for me, but I recall reading Mythical Man Month and thinking about the insights Brooks had from IBM(?) where they...

Sean Lange (5/5/2014)

---

Phillip.Putzback (5/5/2014)

---

Do you use a naming convention for lookup tables so report writers have a way of noticing them before they go create their own? Their own schema...

OCTom (5/2/2014)

---

A friend of mine recently made a wireless device to light up and make a sound when he hit a target on the shooting range.

It was interesting to...

We have a database that we store all of our 'reference' type tables like this. We just try to give it a descriptive name and let everyone know about...

Joining to a lookup table is the way we've got around a similar issue, ever changing values from users. And for the example of midwest states, we have a...

Sean, Your code looses the last value in the string, for value 'asdf12345678901' you loose the 1.

That's wierd I'm having trouble posing code now, Oh well.

Added a 1 + to...

Sean's version seams to work with the data shown, but if the field is a larger field it doesn't always get the correct results. I used a CASE statement...

Your calculation is a bit off, you said "13m record reads per hours / 2,163,568,622 rows = 166 days to create this index !"

That's 166 hours not days, still 7...

Matt Miller (#4) (4/23/2014)

---

below86 (4/23/2014)

---

Good to know, I wasn't aware that it rounded up.

It is wierd that if you do .998 it shows as .997.

declare @d datetime;

set @d = '2014-04-23...

Good to know, I wasn't aware that it rounded up.

It is wierd that if you do .998 it shows as .997.

declare @d datetime;

set @d = '2014-04-23 23:59:59.998'

select @d

Lynn Pettis (4/23/2014)

---

below86 (4/23/2014)

---

Wouldn't it be better to use the BETWEEN with these dates?

WHERE (ath_postype = 'NTC' OR ath_postype='NTD')

AND ath_postdate BETWEEN '2013-01-01 00:00:00.000' AND...