Login | Register   
Twitter
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX


Tip of the Day
Language: Enterprise
Expertise: Advanced
Mar 21, 2000

Handle Ambiguity with Cutoff Year in SQL Server and OLE Automation Objects

While SQL Server uses 2049 as the cutoff year for interpreting dates, OLE Automation objects use the year 2030. To provide consistency in date values between SQL Server and client applications, it is useful to set the two-digit year cutoff option in SQL Server so it interprets a common year as the cutoff. However, to avoid ambiguity with dates, use four-digit years in the data.

For example, if the two-digit year cutoff is 2030 (2049 is the default), the two-digit year 30 will be interpreted as 2030 and the two-digit year 31 will be interpreted as 1931.

Jai Bardhan
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap