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

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: Installing SP4 on SQL 2000
    ... SQL Server 2000 SP3a, x86 ... It seems like there is issue on your install. ... MCITP: Database Administrator ... "David G" wrote: ...
    (microsoft.public.sqlserver.setup)
  • RE: Installing SP4 on SQL 2000
    ... As you said this is a fresh install, so it should not be an issue. ... If you are installing are installing a fresh version of SQL Server 2000, ... MCITP: Database Administrator ... "David G" wrote: ...
    (microsoft.public.sqlserver.setup)
  • Re: Why do I need to restart the SQL service?
    ... > I use Wise Installation utility to install MSDE 2000A. ... what I do within the app is: ... Check to see if the database exists. ... > SQL Server does not exist or access denied. ...
    (microsoft.public.sqlserver.msde)
  • Re: SQL SERVER 2008 Express + SP1
    ... Again there are three service pack setups which are provided by Microsoft. ... Are u sure you are using correct version for your install? ... DB Dev SQL Server 2005 ... Script level upgrade for database 'master' failed because upgrade step ...
    (microsoft.public.sqlserver.setup)
  • Re: sa password was inadvertently changed. With a kicker...
    ... Call the vendor of the new software product, and ask them what the> install script sets the SA password to when installing the product. ... Put the database files back where they should> be, ... >> I have a SQL Server 7 Standard edition server running in a ...
    (microsoft.public.sqlserver.security)