Re: Password History in SQL Server

From: Laurentiu Cristofor [MSFT] (LaurentiuCristoforMSFT_at_discussions.microsoft.com)
Date: 11/18/05

  • Next message: kmsavage: "DSN setting for strong encryption"
    Date: Fri, 18 Nov 2005 10:30:11 -0800
    
    

    That is right: On Windows 2003, SQL Server 2005 can enforce the Windows
    password policy. The password history length is determined by the Windows
    policy in that case. You can display the policy settings by running
    secpol.msc.

    Thanks

    -- 
    Laurentiu Cristofor [MSFT]
    Software Design Engineer
    SQL Server Engine
    http://blogs.msdn.com/lcris/
    This posting is provided "AS IS" with no warranties, and confers no rights.
    "Dan Guzman" wrote:
    > > SQL Server 7.0, 2000 and 2005 do not keep password history.
    > 
    > Mike, I believe SQL 2005 indirectly provides a password history policy under 
    > Windows 2003 when with the CHECK_POLICY option is ON.  SQL Server calls the 
    > Windows NetValidatePasswordPolicy API to enforce local server password 
    > policies.
    > 
    > -- 
    > Hope this helps.
    > 
    > Dan Guzman
    > SQL Server MVP
    > 
    > "Mike Epprecht (SQL MVP)" <mike@epprecht.net> wrote in message 
    > news:uJZeRYw5FHA.2984@TK2MSFTNGP14.phx.gbl...
    > > Hi
    > >
    > > SQL Server 7.0, 2000 and 2005 do not keep password history.
    > >
    > > If you have a need for this, use NT Integrated Security and then that is 
    > > done at AD level.
    > >
    > > Regards
    > > --------------------------------
    > > Mike Epprecht, Microsoft SQL Server MVP
    > > Zurich, Switzerland
    > >
    > > IM: mike@epprecht.net
    > >
    > > MVP Program: http://www.microsoft.com/mvp
    > >
    > > Blog: http://www.msmvps.com/epprecht/
    > >
    > > "SRV" <SRV@discussions.microsoft.com> wrote in message 
    > > news:CB0A689E-7AB6-47FA-AADD-8F774F390974@microsoft.com...
    > >>I know that there is a rule in SQL Server password naming that last n 
    > >>number
    > >> of password cannot be used. Can anyone tell me how much is this n?
    > >>
    > >> Thanks in advance
    > >>
    > >
    > > 
    > 
    > 
    > 
    

  • Next message: kmsavage: "DSN setting for strong encryption"

    Relevant Pages

    • Re: Slow booting xp home.
      ... Changing the boot order to boot first from your hard disk might save you a half second, but you won't be able to boot from a CD until you change it back - and the time spent to do that will erase any previous time saved. ... 2- Consider what software you really want to start with Windows and also how you've configured your applications at startup ... Installing and Registering Visual Studio Express Editions Smart Device ...
      (microsoft.public.windowsxp.perform_maintain)
    • Re: Slow booting xp home.
      ... Thirty seconds to boot Windows? ... I read somewhere that Microsoft suggest 30s boot up on xp home, I have seen videos on youtube of 8s boot up on xp, I'd be delighted with 30s and happy just to get below a minute. ... Installing and Registering Visual Studio Express Editions Smart Device ...
      (microsoft.public.windowsxp.perform_maintain)
    • Re: Security Policy
      ... Windows 2000 is reapplying its Group ... >> A weired thing happened on my SQL Server 2000. ... >> Security policy in the Group policy objects are applied ...
      (microsoft.public.win2000.security)
    • Re: Remote connection failed
      ... If you are going over a remote connection or are not logging ... into the domain where SQL Server is then no, Windows ... authentication won't work. ...
      (microsoft.public.sqlserver.connect)
    • Getting to the bottom of MSDE network connection problems ...
      ... but other than that it is MSDE 2000 with sp3a already applied. ... I've finally figured out the connection problems associated with this, ... and it seems the problems are due to Windows XP and not MSDE. ... the enterprise/standard versions of SQL server won't install ...
      (microsoft.public.sqlserver.msde)