Adding password complexity and password expiration to SQL Server logins is one of best feature I quote for SQL Server version 2005 onwards, similarly such password complexity policies are designed to deter brute force attacks by increasing the number of possible passwords. When password complexity policy...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
04-30-2008
Filed under: sql server, microsoft, security, feature, password, best practice, trustworthy, computing, logins, policies, settings, check_policy, check_expiration
Here is a quick snippet on enabling a SQL login to password expiration and password policies as per the Windows server: Open the SQL Server 2005 Management Studio. In the left pane, go to the desired server and navigate to the Security folder and expand it. Expand the Logins folder. Right-click on the...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
01-07-2008
Filed under: sql server, security, windows, BOL, password, best practice, authentication, books online, policy, logins, sql authentication
I know it sounds easy to upgrade a SQL Server Cluster environment from 2000 to 2005 version, as easy it mentioned within the Books Online for SQL Server 2005. When I have performed for the first time, my first thought was (do we need that or take out the reasons). But one thing is sure that SQL Server...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
11-16-2007
Filed under: sql server, restore, high availability, backup, security, upgrade, best practices, cluster, 2000, 2005, detach, attach, data files, logins