Re: sql2005 enforce user change password in 30 days

I'm guessing that you mean SQL Server logins. Windows-based logins are
secured by the Windows security policies (LocalSecurityPolicies or
DomainSecurityPolicies). In SQL Server 2005, when run on OSes that support
it (Windows Server 2003 and above), you can enforce the (same) local or
domain policy by specifying CHECK_POLICY = ON, CHECK_EXPIRATION = ON in the
CREATE LOGIN or ALTER LOGIN statement. Then SQL Server logins will then go
by the same local or domain security policies that Windows logins do. Make
sure that you provide a way in the application for a SQL Server login to
change the password (all "modern" SQL Server database API support this with
API calls). Otherwise you'll need to use SQLCMD or SSMS to change passwords.

Cheers,
Bob Beauchemin
http://www.SQLskills.com/blogs/bobb


"mecn" <mecn2002@xxxxxxxxx> wrote in message
news:O9PutGIyHHA.3364@xxxxxxxxxxxxxxxxxxxxxxx
Hi,

How do I set up sercurity enforcement to have users change their sql
passwords every 30 days?

Thanks



.

Relevant Pages

  • End User Security Administrator for a Intranet Application
    ... This will involve creating sql server logins and ... administrator needs the SQL server fixed server ... I really don't want to give end users the sysadmin fixed ...
    (microsoft.public.sqlserver.security)
  • Re: access deny the sa account
    ... > authority, is it possible to disable the account sa to access the ... not with SQL Server logins. ... Andrea Montanari (Microsoft MVP - SQL Server) ...
    (microsoft.public.sqlserver.msde)
  • Re: Cross VPN Domain Authentication
    ... around having to maintain those SQL Server logins and the user ambiguity ... SQL Server DBA ... Children's Oncology Group ...
    (microsoft.public.sqlserver.security)
  • Re: Distributor SQLSERVERAgent Account
    ... accounts and SQL Server logins. ... a domain user account if you are to replicate from one ... >running SQL Server Agent as LocalSystem and sa? ...
    (microsoft.public.sqlserver.replication)