all groups > sql server connect > october 2004 >
You're in the

sql server connect

group:

Problems connecting to SQL-Server


Problems connecting to SQL-Server Olav
10/25/2004 8:23:03 AM
sql server connect:
Hi,
we have an customer trying to run our app. after installation. They get the
error messeage: Login failed for user skdomain/skuser.
Our app uses ADO.NET and the database is MS SQL Server. The program and sql
server is installed on a separate server. To run the app. they have 8
application servers with metaframe. Our app is set up to connect to the
database using WIN NT autentication.
Re: Problems connecting to SQL-Server Sue Hoegemeier
10/26/2004 3:52:51 PM
Is skdomain\skuser been granted access with a login in SQL Server? Do
they have the required users added to the server as well as setup as
users in the database?

-Sue

On Mon, 25 Oct 2004 08:23:03 -0700, "Olav"
[quoted text, click to view]
Re: Problems connecting to SQL-Server Olav
10/27/2004 3:37:04 AM
Hi Sue,
i dont follow you here. My be because i use a standalone XP Pro PC?
Where do i "click" to grant access with a login in SQL Servers? Can i see it
on my PC or must i use my customers?

Olav

[quoted text, click to view]
Re: Problems connecting to SQL-Server Olav
10/27/2004 6:47:06 AM
Thanks Sue,
this can take som time when there is 200 users to add?
May be a faster approach is to use SQL authentication.
Then it would work with only one user registered the same place?
Is there a difference in connection speed with NT and SQL authentication?

Olav


[quoted text, click to view]
Re: Problems connecting to SQL-Server Sue Hoegemeier
10/27/2004 7:05:03 AM
You won't see skdomain\skuser on your PC. A windows login is
specific to the domain or workgroup. When using windows
authentication, any login you want to have access to SQL
Server needs to be added as a login for SQL Server. In
Enterprise Manager go to Security and then to Logins. Right
click on select New Login. Click the button to the right of
the Name text box and you will pull up the domain or
workgroup logins that you can add as logins for SQL Server.

-Sue

On Wed, 27 Oct 2004 03:37:04 -0700, "Olav"
[quoted text, click to view]
Re: Problems connecting to SQL-Server Sue Hoegemeier
10/27/2004 8:46:09 AM
When you have a lot of users, it's generally more efficient to use
Windows groups rather than individual Windows logins. Another
consideration is that you don't necessarily have to use just
Enterprise Manager to add the logins - you can execute sp_grantlogin
to grant a windows account login access to SQL Server. You can use
sp_grantdbaccess to allow the login access to a database. This can
give you more flexibility in terms of building a script the users
access.
There is no real performance difference between the two authentication
modes. Windows Authentication is more secure than using SQL logins.
You may also want to check SQL Server books online and read up on
application roles as that may be something you would want to look
into.

-Sue

On Wed, 27 Oct 2004 06:47:06 -0700, "Olav"
[quoted text, click to view]
Re: Problems connecting to SQL-Server Michael C
10/28/2004 1:44:04 PM
Using a single SQL Server auth login for 200 users is not very secure.
Although I'm sure the DBA will probably appreciate getting out and talking
to all 200 employees every time he decides to change that password.
Tracking down any security issues should be easier, since you don't actually
have to track 200 users; just track the one login and blame all 200 users!

[quoted text, click to view]

AddThis Social Bookmark Button