SQL Server 2005 actually shipped with code that used the local time instead of UTC time in CREATE CERTIFICATE. Users in Western hemisphere (local time behind UT

SQL Server 2005 actually shipped with code that used the local time instead of UTC time in CREATE CERTIFICATE. Users in Western hemisphere (local time behind UTC) had no major problems because of it, but users in Eastern hemisphere (local time ahead of UTC) would create certificates not yet valid. Confusing, to say the least. See http://rusanu.com/2008/08/25/certificate-not-yet-valid/ http://rusanu.com/2008/08/25/certificate-not-yet-valid/