SQL Server: February 29, leap day

  • Article

Introduction

February 29, also known as leap day in the Gregorian calendar, is a date that occurs in most years that are divisible by 4, such as 2008, 2012, 2016, 2020, and 2024. Years that are divisible by 100, but not by 400, do not contain a leap day. Thus, 1700, 1800, and 1900 did not contain a leap day, 2100, 2200, and 2300 will not contain a leap day, while 1600 and 2000 did, and 2400 will. Years containing a leap day are called leap years. February 29 is the 60th day of the Gregorian calendar in such a year, with 306 days remaining until the end of the year. (From the Wikipedia)

What is better to publish on Fabruar 29 then

This article published on February 29 2016, which is a good date to start discuss some of the weird behaviors (or BUGs) people experience regarding February 29 in SQL Server, from Transect-SQL to the SQL Engine behaviors and result.

Most people heard about the 2000 bug, which occur once in 1000 years, but less people familiar with much more common bugs related to February 29, which occur approximately every 4 years. Let's named then as the "February 29 bug". 



http://www.w3schools.com/css/img_trans.gif

>>>>>>>>>>>>>>> under construction <<<<<<<<<<<<<<<