Connection to a MS SQL Server Table (newbie)

I am getting started on a prototype site and have set up one of my home
machines with IIS and MS SQL Server. Based on several on the posts to this
group, I have been reviewing the ADO connection strings. However, what
really puzzles me is that it appears you need to use an unsecured SQL Server
(no user name and no password) or provide the username and password in the
connection string. The latter seems to defeat the purpose of a password.

What I am guessing at this point is that a SQL server account needs to be
set up with the only the necessary permissions to get the job done. Is this
correct?

In the bigger picture (might be a vision or a hallucination!), this site
will be a secure site (https://) with username/password access. It is
basically a departmental personnel database tailored to our specific needs.
The objective is to provide some limiting of access based on groups and work
units (i.e. Group Lead A can only view the people organizationally below
him).

Any comments, thoughts, references, etc will be greatly appreciated!

Thanks!

Don



.

Relevant Pages

  • Re: SQL Express 2005 doesnt support multiple users....
    ... > database should specify the same connection. ... With user instances, you are ... > Express) and set both client connection strings to ... > Jasper Smith (SQL Server MVP) ...
    (microsoft.public.sqlserver.connect)
  • Re: Connections String Questions
    ... As far as Q1 - always use SqlClient with a SQL Server or SQL Express ... Help on connection strings to see what best suits your application. ... Which provider should be preferred when defining a connection, ... I have a database on my local PC and the same ...
    (microsoft.public.dotnet.framework.adonet)
  • OLAP connection problems
    ... I have two systems setup with SQL Server 2000 + Analysis Services. ... servers have been patched with both SP3a patches. ... I wrote a trivial command line app that tests connection strings through ... It is very frustrating to get an absolutely generic error message. ...
    (microsoft.public.sqlserver.programming)
  • Re: data access strategy
    ... there must be a Domain in your LAN so that you and your users can connect to your SQL Server instance using Windows Authentication. ... Also, you did not mention if 8082 is a static or dynamic port but that's for sure it's not the default port so you must be using a Named Instance instead of a Default Instance and it means that your Named Instance will be using dynamic ports by default and if it uses a dynamic port, it means that this dynamic port will be changed when your SQL Server service restarts. ... I've tried all manner of connection strings to connect remotely. ...
    (microsoft.public.sqlserver.connect)
  • RE: Allowing user selection of a datasource at run time?
    ... but you can build connection strings to connect to any OLEDB ... the SQL Server instances, which is much easier. ... I need to allow> a user to select a database to connect to at run time via a standard dialog> box. ... This causes the 'Data Link Properties' dialog box to appear> which allows the user to select an OLEDB data provider, and a database, etc. ...
    (microsoft.public.dotnet.framework.adonet)