Re: Installation OK, but can't connect
From: Andrea Montanari (andrea.sqlDMO_at_virgilio.it)
Date: 03/08/04
- Next message: Andrea Montanari: "Re: Isn't DROP DATABASE definitive?"
- Previous message: NWx: "Best strategy on storing files on server"
- In reply to: Daniel Strigard: "Re: Installation OK, but can't connect"
- Next in thread: Daniel Strigard: "Re: Installation OK, but can't connect"
- Reply: Daniel Strigard: "Re: Installation OK, but can't connect"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 8 Mar 2004 17:09:07 +0100
hi Daniel,
"Daniel Strigard" <anonymous@discussions.microsoft.com> ha scritto nel
messaggio news:8ec501c4051d$8c49e520$a501280a@phx.gbl...
> >SQL Server authentication is "client" independent....
> that's to say you can
> >connect with the same credential from any client on you
> lan
>
> I'm not sure I understand you here. You say on "my lan".
> Does that mean that it has to be on my specific lan? What
> about other computers, not on my lan, using my program?
all clients have to specify the server name they want to connect to in the
form ComputerHostingSql_Name(\instanceName if named instance)
on your lan the server name is YourComputerName , while on my lan the server
name is SQL2K-SOLE , which is the name of the computer hosting the default
instance of SQL Server we are using...
so your connection string must not be hardcoded, becouse the server name is
variable.....
> Do I use the server=local command then? And what about
> granting access to user groups, when I don't know what
> kind of user groups there will be on another computer?
> It seems to me from what you've said that neither WinNT or
> SQL Server authentication is perfect for me...although I
> can't say I fully understand all of this yet.
granting login and access permission is usually done once the SQL
Server/MSDE instance has been deplyoed to the end user....
if you are using WinNT authentication, the end-user's sysadmin must choose
the Windows Logins/Groups to whom grant login privilege to SQL Server....
if using SQL Server authentication, the end-user's sysadmin must create the
SQL Server's login for each user to whom grant login privilege to SQL
Server....
then, the end-user's sysadmin must grant database access to each login (or
SQL Server role, if you managed your security that way)....
please have a look at
http://www.microsoft.com/sql/techinfo/administration/2000/security/default.asp,
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops3.mspx
,
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sp3sec00.mspx
enjoy =;-))
-- Andrea Montanari (Microsoft MVP - SQL Server) http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org DbaMgr2k ver 0.6.0 - DbaMgr ver 0.52.0 (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual interface) --------- remove DMO to reply
- Next message: Andrea Montanari: "Re: Isn't DROP DATABASE definitive?"
- Previous message: NWx: "Best strategy on storing files on server"
- In reply to: Daniel Strigard: "Re: Installation OK, but can't connect"
- Next in thread: Daniel Strigard: "Re: Installation OK, but can't connect"
- Reply: Daniel Strigard: "Re: Installation OK, but can't connect"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
