Implementing security in Sql Access application

Thanks for your kind advice. I will take a look at it as a starting point.

"Erland Sommarskog" wrote:

> Jack (Jack@discussions.microsoft.com) writes:
> > I inherited an application written in sql access. Currently the
> > application does not have any security. However I have to implement
> > security in this application. I know how to work with Access security.
> > However I am trying to avoid that. Instead I am trying to come up with
> > sql server security. I have not worked on sql server security before. Is
> > it possible to secure Access Sql application using just sql server
> > security? If it is yes, is there any article that would give me some
> > idea as to how to implement security in the present scenario. Thanks in
> > advance.
>
> Since I don't know what your security issues are it's difficult to give
> specific advice, but Books Online as a section on security. That could be
> place to start.
>
>
> --
> Erland Sommarskog, SQL Server MVP, esquel DeleteThis @sommarskog.se
>
> Links for SQL Server Books Online:
> SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
> SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
> SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>
>
 >> Stay informed about: Implementing security in Sql Access application 

If you know how to work with role-based security in Access, it's
pretty much the same as SQL Server, except reversed. What I mean by
that is by default Access security is turned off, and in SQLS it's on.
You must explicitly grant permissions, and instead of everyone being
in Admins by default with full rights, they are in the public role by
default. Another different wrinkle is that there's server level
security and database level security, so theoretically someone could
log on to the server and not be able to connect to a database. What's
the same is you never grant permissions to users, only to roles, and
then add users to roles. In SQLS 2005 and 2008 you also have schemas,
which gives you a little more flexibility. So this is already getting
confusing, right? Even though you're using Access and not ADO.NET,
this conceptual topic explains the basic concepts and has links to
relevant topics in SQL BOL. See
http://msdn.microsoft.com/en-us/library/bb669074.aspx.

--Mary

On Thu, 11 Dec 2008 14:19:02 -0800, Jack
wrote:

>Hi,
>I inherited an application written in sql access. Currently the application
>does not have any security. However I have to implement security in this
>application. I know how to work with Access security. However I am trying to
>avoid that. Instead I am trying to come up with sql server security. I have
>not worked on sql server security before. Is it possible to secure Access Sql
>application using just sql server security? If it is yes, is there any
>article that would give me some idea as to how to implement security in the
>present scenario. Thanks in advance.
 >> Stay informed about: Implementing security in Sql Access application