Re: How to install and configure SQL Server 2005 on Net work and s

Hi MS,

Thank you for your opinion. I am sorry maybe my description is not clear. I
would like to go simple way to describe my question below, I hope I can make
question clear to you to get your help.

1. What is purpose for set "Window Authentication" or "Sql Server
Authentication" or mix both when I install SQL Server 2005? this seting only
for DBA to login to do dabase management in future? no matter with Client
(User)?

2. Should DBA still need to set Permission (User name and Pass word) to
Client (user)? even If Client (user) don't need to login to Sql server
database, They just using fron client-server application which mean is that
application have fron-table linked to back-ed Sql Server DB?

I am really comfusing on those points which I describe above


Thanks a lot


Henry


"MS" wrote:

I'm not sure I followed all your points, but I would, in the general case,
use windows authentication and, if possible, I'd leverage a domain server to
centralize my windows account administratation. This way, on the sql server,
you get to control permissions using rolse that map onto ActiveDirectory
domain groups (and from there to the end user account).

They logon to windows and then SQL Server handles the rest based on the
permissions you have given


"Henry" <rfahangmin@xxxxxxxxx> wrote in message
news:8BAAA53E-D568-402D-A50D-B8FF7E113ACD@xxxxxxxxxxxxxxxx
Hi MS,

Thank you very much for your opinion and I am glad that you spent time to
write this important information (at least for me).

I think best way I world like let you know what is my purpose to set up
back-end Sql server.

1. the purpose is only would like to split all tables from front ACCESS
database to backend and then link all table from front Access database to
backend.

2. I already set a security permission with .mdw to individule user or
group
when user try to open forms and reports in front Access database.

3. we never allowed user can login to sql server to do any thing, that
mean
is that only allowed user using front end all applications

4. base on three points above, Do you suggest that I still should set
User
name and pass word for those users, after I installing and configurating
the
Sql server 2005 ? but only thing is that the front tables link to back-end
DB
automatically when
user runing every application on fron-end in network envieronment.

5. Each user they required Windows Authentication when they open they won
computer in our Org. Not for using ACCESS databse as usualy, Also they
reuqired login after lohin Widows if someone want to using ACCESS DB's
applications.

6. I am confusing on seting security is that whether I set mix
authentication during I process installation of Sql server, only for me
which
is database administrator? because it will required pass word and user
name
when i login to Sqlserver to create table for something in Sql server in
future?

7. As I described above, If user just using front-end application with
linked table, Should I set up pass word and user name for those users?
because they using linked table from front applicatio?

8. In my case, each employee have window authentication for general
purpose
when they turn on their PC (not for using access db), Can I ask them to
get
their user name and pass word as Sql server "Window Authenticatio"? if
neccesary to set up user's security because user using front-end liked
table.
So that is why I am getting confusing.

I really reaaly appreciate it if you and help me to get out those
confusing.

Thanks a lot


Henry


"MS" wrote:

The server authentication property is really just an option for
administrators. They may want to lock down security so that all
authentication is done at the ActiveDirectory level, in which case they
would select Windows Authentication. Maybe they want flexibility, allow
people to logon as integrated windows logins or as SQL server
administered
logins, whatever is more convenient, in which case they'd choose mixed.
If
they have no windows-level authentication domain, they may then prefer to
keep it simple and limit logins to sql server authentication.

Not sure what you mean by question 2. You have to have an OS in order to
install the sql server. You may want to keep the SQL Server machine
separate
from server's running other cpu-intensive applicaitions, but that is
another
question altogether.

Best way to test is to run up management studio, see if you can connect
and
see if you can browse databases and tables

"Henry" <rfahangmin@xxxxxxxxx> wrote in message
news:2FE26825-7B65-495A-8480-5E939D7B26AF@xxxxxxxxxxxxxxxx
Hi Friends,

I am new on sql server database. I try to move all front-end database
which
is attached with MS ACCESS applications. I read several books but
getting
confuse for all. I think because I have no experience on this. Please
help
me
to see questions below.

1. what is purpose for set "Window Authentication", "Sql server
Authenticatio" or both mix? when I install SQL server 2005, this set
only
target to AS? or aa user?

2. Is there best way install sql server 2005 in same machine with OS?
or
seperate
machine?

3. How to test whether installation and cofiguration are succesfully?

I am sorry may be questions too simple for you to waste you time. But I
really appreciate it if you can help me?


Thanks a lot


Henry






.

Relevant Pages

  • Re: System Administrator Implied Permissions
    ... > sa login, it assigns it the System Administrator fixed ... > Now, given this, why does SQL Server ... in each database is always a member of the public and db_owner roles. ... Other sysadmin role members have the exact same ...
    (microsoft.public.sqlserver.security)
  • Re: No db access after publishing web site
    ... GRANT UPDATE TO ... If I detach and attach this database on a different PC (according that PC ... Cannot open database "pago" requested by the login. ... Are you detaching/attaching the SQL Server Express database correctly ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: cannot login to the db after...
    ... Jasper Smith (SQL Server MVP) ... I have created a new database, "db_1", using the "sa" ... I then created a new login, "sqluser1" and gave ...
    (microsoft.public.sqlserver.security)
  • Re: Cant view merge agent properties (trying again)
    ... In the List of Actions for the Snapshot Agent History I see this repeated: ... every single database listed. ... So, just now, I went to computername\Administrator Login ID (because it's ... On the computer running SQL Server, ...
    (microsoft.public.sqlserver.replication)
  • Re: Database security design with ASP.net and form-based authentication
    ... Since you already have forms-based security, why not use a single SQL login ... for all database access? ... data entry, guest/view only, admin, report viewer. ... so I'm using SQL Server authentication. ...
    (microsoft.public.sqlserver.security)