Nice question and correct answer (pity about the locale issue, though).

Unfortunately, the explanation is rather wrong - not surprising, as the BOL page on smalldatetime also gets the rounding wrong.

29.999...

archie flockhart (3/13/2013)

---

I also wonder whether the precision being returned by the SYSDATETIME function might explain the behaviour that Tom highlighted, where the test script runs much faster on his...

Nice question.

A useful reference that should perhaps have been in the explanation is the BOL datetime page which has a information about the ODBC timestamp literals with their literal_type fields...

jcrawf02 (3/12/2013)

---

I have the same understanding of the original premise of XML (simplified SGML that is supposed to promote human-readability within extensible documents), but fail to see how this extends...

Well...

vk-kirov (3/12/2013)

---

This script works up to several minutes on my local SQL Server (Core i5), finally displaying a result like this:

FirstDate ...

Actually I rather like this question. It opens up an interesting bag of worms. Hugo's explanation shows people what they have to do to avoid silly errors (not mix...

deleted duplicate post

ronmoses (3/1/2013)

---

Where I got tripped up was here, and I guess I'm still not sure I understand...

create proc sp1

as

select * from temp1

exec sp2

Without a BEGIN and END defining the body...

These constraints are often called cross-database foreign key constraints. SQL Server offers no support for them, in fact I don't think any widely used commercial SQL database does. ...

David Burrows (3/11/2013)

---

SELECT DISTINCT j.name as job_name,

msdb.dbo.agent_datetime(run_date, run_time) AS [run_datetime],

DATEADD(second,DATEDIFF(second,0,msdb.dbo.agent_datetime(19000101, run_duration)),msdb.dbo.agent_datetime(run_date, run_time)) AS [run_endtime]

FROM msdb..sysjobhistory h

INNER JOIN msdb..sysjobs j ON h.job_id = j.job_id

WHERE j.name NOT LIKE 'Backup%'

AND j.name NOT...

SQLRNNR (3/10/2013)

---

Lynn Pettis (3/10/2013)

---

GilaMonster (3/10/2013)

---

Since it's the msdb job tables, it's a bit of a stretch to say we don't have data. That said, that had a feel of 'do...

Jeff Moden (3/10/2013)

---

My take on it is that just because millions of people are using it, I don't have to think they're right. Unfortunately, because there are millions of...

Hugo Kornelis (3/11/2013)

---

Hmmm, not sure why some people are so critical about this question. Okay, there is an issue with OBJECT_ID instead of DB_ID in query 2, but other than...

It always surpriseded me that anyone relied on it, except in early cobol programs where dates...