SQL Server 2008 Leap Year Issue

re: SQL Server 2008 Leap Year Issue

James Luetkehoelter — Fri, 29 Feb 2008 18:17:37 GMT

Thanks! I very nearly got caught by this as I'm loading it on a new laptop!

re: SQL Server 2008 Leap Year Issue

Denis Ruckebusch — Fri, 29 Feb 2008 18:19:27 GMT

Is there any additional information available regarding the nature of the problem? I am very surprised to see this is a startup/setup issue.

The first thing that came to my mind when I heard there was a leap year problem with SQL Server 2008 was that there was an issue with some of the datetime data types. I didn't even think that setup or startup could be affected by bad leap year calculations.

Also the way the issue is described it looks like it won't be a concern anymore once we roll into March 1st.

I'd love to see exactly what the issue is.

re: SQL Server 2008 Leap Year Issue

Peter W. DeBetta — Fri, 29 Feb 2008 18:26:20 GMT

Couldn't tell you exectly what is going on, only that something is.

I haven't heard or seen any issue with the date and time types.

On a good note, earlier today I started a Virtual PC with CTP6 on it that was previously saved yesterday. Since the service was, in essence, already running, I didn't experience any issues.

re: SQL Server 2008 Leap Year Issue

jerryhung — Fri, 29 Feb 2008 20:24:22 GMT

Mnn, not a good first impression for SQL Server 2008

please let it not be SQL 2005 SP2 mess repeat =P

re: SQL Server 2008 Leap Year Issue

Denis Gobo — Fri, 29 Feb 2008 20:50:19 GMT

Of course I couldn't wait to see this for myself on my virtual pc :-(

re: SQL Server 2008 Leap Year Issue

Peter W. DeBetta — Fri, 29 Feb 2008 20:54:42 GMT

It is a CTP and not RTM. And this is why it is available for public use (AKA the ultimate QA).

re: SQL Server 2008 Leap Year Issue

Geoff — Mon, 03 Mar 2008 22:29:49 GMT

I know the leap day has passed. But did anyone try changing the computer's date and then changing it back.