Creating a SQL Server user authentication schema
Learn how to create a SQL Server user authentication schema having password and tracked data changes requirements and how it involves Windows authentication.
How can I generate a SQL Server user authentication/authorization schema (tables/keys/indexes) to support the following requirements:
Continue Reading This Article
Enjoy this article as well as all of our content, including E-Guides, news, tips and more.
Step 2 of 2:
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.
- A user is required to have a login name, first name, last name, and password.
- A user password will expire in 90 days.
- A user account will be locked after five failed attempts in five minutes.
- A locked account will automatically be unlocked 20 minutes after last failed login attempt.
- A user can change their password but it cannot be the same as any of the last 10 passwords used.
- All data changes have to be tracked and attributable to the person making the changes.
If you are using SQL Server authentication, you will have to put source code in your application to account for "1" and "2". Since SQL Server will be doing the authentication, you won't be able to perform "3" through "6". If you choose to use Windows authentication – more secure with some tradeoffs – you'll be able to set the password complexity and lockout options with a Group Policy Object or Local Security Policy.
This was first published in December 2007
This Content Component encountered an error
PRO+
Content
Find more PRO+ content and other member only offers, here.
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.
Meet all of our SQL Server experts
View all SQL Server questions and answers
0 comments
Oldest Newest