Books Online: CHECK_EXPIRATION Discription Is Inaccurate - by JediSQL

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 800397 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 9/12/2013 9:52:43 AM
Access Restriction Public

Description

ms-help://MS.SQLCC.v10/MS.SQLSVR.v10.en/s10de_6tsql/html/e247b84e-c99e-4af8-8b50-57586e1cb1c5.htm
http://technet.microsoft.com/en-us/library/ms189828.aspx

The "Remarks" regarding CHECK_POLICY  and CHECK_EXPIRATION are inaccurate.  It is stated that "When CHECK_POLICY is changed to ON, the following behavior occurs: •CHECK_EXPIRATION is also set to ON, unless it is explicitly set to OFF."

If you run this batch in either SQL Server 2008 R2 or SQL Server 2012 you will see that is_expiration_checked is always 0 (zero):

create login [aaaaad] with password='1234qwerASDF', CHECK_POLICY = ON ;
select * from sys.sql_logins where name = N'aaaaad'

create login [aaaaae] with password='1234qwerASDF', CHECK_POLICY = OFF ;
select * from sys.sql_logins where name = N'aaaaad'
alter login [aaaaae] with CHECK_POLICY = ON ;
select * from sys.sql_logins where name = N'aaaaad'



Sign in to post a comment.
Posted by Rick [MSFT] on 9/25/2013 at 9:17 AM
Thanks for pointing this out. I have fixed the topic by removing the part where is says that the CHECK_EXPIRATION is automatically ON when policy is ON. This will change in the online versions of the topics as they are republished. Thanks.