October 17, 2007 at 3:38 am
i am asked to give connection to database in the production environment
my question is the database will be connected through an application using .net.
when they double click a login screen will appear. Say ic number of the user is keyed in to login the application
internally when they connect at the place where we give connection to the database will have
sql server name, database name, userid A, password
This userid A Should have what permission and can they select, delete,
insert
Thanks
October 17, 2007 at 7:59 pm
Jai, I understand what you need to do, but I don't know what your question is. Do you need to build the database connection string?
K. Brian Kelley
@kbriankelley
October 18, 2007 at 1:58 am
yes database connection string, what permission should be given and how is should be created in sql server.
October 20, 2007 at 9:08 am
please reply me,
what permission should i give for the userid( dbowner or dbread & dbwrite) in the connection string from the application to connect the db.
Thanks
October 22, 2007 at 12:37 pm
The generally recommended practice is to put all the data access code (select, update, insert, delete) in stored procedures in the SQL Server database and grant the database user EXECUTE permission for the stored procedures. That way, the user doesn't need any permissions for the tables. I would never make an application user a member of dbowner.
Greg
Greg
October 23, 2007 at 10:10 pm
Greg, please help with the script to set these permissions.
Thanks
October 24, 2007 at 5:11 pm
The connection string doesn't provide the permissions. Permissions must be on the objects, such as tables, views, stored procedures, and the like, as previously indicated. In order to do this, you have to understand how the objects are going to be used.
K. Brian Kelley
@kbriankelley
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply