This should be an easy question to answer...
I'm trying to connect to my SQL Server 2005 (running on localhost) from the code-behind of a test webpage that I made. The connection string I'm using is:
Data Source=localhost;Initial Catalog=dbname;User Id=username;Password=password;Timeout=160
I think the reason I'm confused is that I can't create a user in Yukon like in 2000, assigning it a username and password. In Yukon, there's no option to create a password for a user... I saw that I can create a username and password if I create an application role, so is this what I'm supposed to use?
Whenever I create a user or application role and try to connect to it w/this connection string, I get:
No process is on the other end of the pipe.
If I make the user or application role the owner of the db_owner schema then this error message goes away but I then get:
Invalid login for user ____
I already made sure that I have tcp/ip and named pipes enabled for local and remote conns.
Lastly, when I create a user, I have to give it a login name, which is a windows user account, so I have no idea what to put for that.
So I guess my question is, what is the proper way to set up a user or application role in sql server 2005 and then be able to connect to it w/ado.net 2.0?
Thanks,
JustinThere two permissions in SQL Server the server permissions in SQL Server 2005 are still under security in management studio but the database permissions are now under security in the database. Hope this helps.|||Thanks for the quick response, but what you posted is what I already know...
Can anyone give advice on how to set up a user or application role properly to be used from an application. Which is more appropriate to use: app role or user? What schema should be set for them? What permissions should be given to them?
Thanks,
Justin|||The answer I was looking for was "Logins".
No comments:
Post a Comment