Authentication

I have 2 instance on SQL Server, One remote the other local. Both authenticate via window NT.
How can I change one or both?
To connect to a application do I setup a usergroup? Grranted this is still in the testing stages.How can I change one or both?

Huh? (Was not a long enough message...)

If they want to parse something, they should parse the questions...|||1. How can I change one or both for authenicating throw SQL Server & Windows. From the application standpoint eash database within the instance could have restricted access.

2. Most user will only have access to the data via there particular application that interfaces with the dataBASE. Would you say this would fall under the category of Usergroup Brett. Where your buddy, who always has great instinct and insigght.|||I'm sorry...

Are you saying 1 Application is connecting to multiple databases?|||No, application Users should have access through authentication of Windows NT. If it's a outside user(offsite) and I want to make fo-sure he is allowed to have access. How would that be done.|||Are you planning to change server authentication mode from Windows Only to Mixed through FE code?|||Yes, that sound like what I'm looking for. What is FE Mode?|||FE Mode? It's front-end code ;)


Authentication mode is not a dynamic property. And I don't think that "messing" with server security is a proper role for an application. Any thoughts?|||The connection string you use will determine how you authenticate to the SQL Server. If you specify a User ID and a Password, then you will be authenticated based on the SQL Login. If you supply Integrated Security=SSPI, then you get windows authentication. Windows authentication is preferred, in case you try to put both in.

From this, you could try to modify the connection logic of the application to chose a connection string on startup. Or are the people in fixed locations just on different sides of the firewall?|||Mixed authentication. Different sides of the firewall using VMware product as the base repository. It come down to setting up the agent on the user site with the proper setting. After all they dont have access through EM, Just there application.

Thanks|||It's in the profile Check out the attachments