Connecting client applications to sql server

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » SQL Server 2005 General Discussion » Connecting client applications to sql server

Connecting client applications to sql server

Rate Topic

Display Mode

Topic Options

Author

Message

sam_invincible1

Posted Sunday, May 25, 2008 1:30 AM

Forum Newbie

Group: General Forum Members
Last Login: Wednesday, May 28, 2008 9:04 AM
Points: 6, Visits: 34

i am confused between windows authentication and sql server login , how is windows authentication more secure? what domain name should we give in assigning sql server login account? where should we get the domain name? how would a client connect to the server instance if he is not in the local network?
how to create a connection between client and server ? could anyone please clear this ....thank you :-(

Post #506310

Phillip Cox

Posted Sunday, May 25, 2008 1:50 AM

SSCrazy

Group: General Forum Members
Last Login: Friday, October 12, 2012 7:55 AM
Points: 2,133, Visits: 604

sam_invincible1 (5/25/2008)

Hi,

Here is a good link, which will provide you with a great overview, but overall, Windows security is more secure than using SQL Server authentication and simplifies user management. In terms of domain name, you will need to have a pre-built Windows domain prior to being able to use Windows authentication, otherwise you will not be able use this security method. If a client is not on your local network, you will need to configure your setup using mixed-mode security for your SQL Server's instances, as you will only be able to authenticate user's of this type via SQL Server security model.

http://msdn.microsoft.com/en-us/library/ms144284.aspx

Hope this helps!

Phillip Cox
MCITP - DBAdmin|MCTS - SQL Server 2005|MCP - SQL Server 2000

Post #506311

« Prev Topic | Next Topic »

Permissions