Re: Database setup with Windows Installer

You have 2 types of security for SQL Server, Windows Authentication and SQL
Server Authentication. The 1st requires a Windows account, the 2nd does not.
If you use Windows, each user will have to have their Login added to the
Server and to the database (unless you put them all into a NT Group, and
give that group permissions to your server and DB). If you use SQL
Authentication, many people can share the same login (but you won't be able
track who does what).

One way to do this is to run the sp_addlogin in your script, it is
documented in SQL Server's Books Online.
This creates a new Microsoft® SQL ServerT login that allows a user to
connect to an instance of SQL Server using SQL Server Authentication

After the db is installed your app that connects to the db could provide an
input form that collects the ID and password, unless you are using Windows
Authentication and in case the user can be logged in silently .

This whole topic is NOT simple.

"Bagger" <Bagger@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:37B58C0B-0FFB-49A5-A94F-62C733B3788E@xxxxxxxxxxxxxxxx
> I've got an application that requires a SQL Server database. I have added
> a
> custom action to my setup project to create the database during the
> install.
> That part works fine. What I need to do now is set up a user for the
> database. That's what I'm not sure how to do. During development, the
> app
> has simply logged in as the 'sa' user. I'm definitely not a SQL Server
> expert, so I'm not really sure what needs to be done to create a user that
> the application can login as. From what I can tell, it looks like I need
> to
> have a database user set up, and that user needs to be tied to a Windows
> account. What info do I need to prompt the user for during installation,
> and
> how do I use that info to set up a user for the database that my
> application
> can use to login?


.

Relevant Pages
Quantcast