Adding User to SQL Server

Question

Adding User to SQL Server

Paresh MD

SSC Rookie

Points: 41
More actions
September 5, 2013 at 9:13 am

#282143

Hi,
I got a scenario where I am using Windows Application.
I want to create a SQL Server User satisfying the password policy. I have couple of questions related to it.
1. How can I create such a user?
2. After creation of the user, I want to store its password somewhere at a central location[don't know where? can somebody help?]. While connecting to DB, read this password from central location on the network and login to SQL Server.
Please help.
Thanks,
Paresh

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Sean Lange SSC Guru Points: 286573 More actions · Answer 1

Paresh MD (9/5/2013)
Hi,
I got a scenario where I am using Windows Application.
I want to create a SQL Server User satisfying the password policy. I have couple of questions related to it.
1. How can I create such a user?
2. After creation of the user, I want to store its password somewhere at a central location[don't know where? can somebody help?]. While connecting to DB, read this password from central location on the network and login to SQL Server.
Please help.
Thanks,
Paresh

Why are you going to store the password somewhere else? The idea of a password is that it is protected. If you are just going to store it in plain text elsewhere why do you care if it satisfies the password policy? Generally speaking if you are creating this user so that an application can use it you would store the connection string in the app.config or some sort of config file.

You can read up on creating a user here. http://technet.microsoft.com/en-us/library/ms173463.aspx

_______________________________________________________________

Need help? Help us help you.

Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/

SQL Surfer '66 SSCertifiable Points: 5161 More actions · Answer 2

Can't you use Windows authentication (Active Directory account)? No need to worry about password policy and certainly no need of storing the password.

kevaburg SSCoach Points: 18131 More actions · Answer 3

SQL Surfer '66 (9/6/2013)
Can't you use Windows authentication (Active Directory account)? No need to worry about password policy and certainly no need of storing the password.

I would second that. Creating the account in Active Directory, preferrably as a member of an AD Group, keeps the account in a central location, allows Group Policy to determine the password policy and reduces the vulnerability surface area of your server by removing the need to have SQL Server Authentication turned on.

Just remember that not all your users need to be SYSADMIN...... 😉

sqlnaive SSCoach Points: 17437 More actions · Answer 4

I second these guys on security. Windows authentication is best way of providing secuiryt to users. AD group can be defined for group of users requiring saem level of permissions.