I have set up a SQL database for my client's WebConnect application using the Create SQL Server Tables Wizard. So far, I have only set up my WebConnect tables with my own SA access to everything on all databases and tables.

Now I want to give a client access to a single database

To set up their access to the MS SQL tables in a single SQL Database (without granting access to any other databases), what settings should I set up for them and their application under [Database Name] - Security - Users - [User Name]:

• Owned Schemas
• Membership
• Securables
• Extended Properties

They'll want to access their data (of course) but also allow their WebConnect application to save its logs to the table.

TIA

I would not put the wwrequest/wsession tables in the same DB your application data lives in. At a high level, you're going to want to separate the framework's SQL access from your application's SQL access.

Of course - I'm referring to only the wwrequestlog/wsession/wws_id tables for this question.

I'm using SQL for the ww tables in my application. I've assigned the standard data_reader and data_writer roles to a dedicated SQL login. Haven't done anything with the other items you mentioned.

I often wonder exactly what's required. SQL Server can be very finicky with permissions in some cases, but for application users Data_Reader and Data_Write is usually all that's needed.

+++ Rick ---