Hi,
I have made a web application using SQL Server 2005Express with a few admin pages that require login. I used the SQLServer Managment Studio Express to setup users and groups and it worksfine.
But the web server has SQL Server 2000 and all I get is auser id and password to access the database. It seems I cannot use theLogin control I put on my "login.aspx" page becuase it uses theintegrated authentication which chokes on 2000. I am afraid I wonlt beable to use some of the 2.0 features such as profiles, ...
Isthis the way 2.0 works with SQL Server 2000? Should I ditch the ISP ifthey only give me a single access to database with no provisions tocreate users. (I was told I had to create a "Users" table and manuallyassign ids and passwords and that I can only use the user id andpassword they supplied to setup the connection string in the script.)
I appreciate your help.
Single login connectionstrings are the more natural way to do something like this - the 'users' you are referring to, are users of your application, and don't need to be users in the database - you wouldn't want them to have access to your database, in fact.
And you can easily setup a membership/roles scenario, in the database (2000 or 2005) with the connectionstring they give you.
|||Thanks for the info.
When is it appropriate to add users and groups using the SQL Server Management Studio?
Canyou please point me to a document or article that describes how tosetup and use membership/roles using only the connection string?
Thank you.
No comments:
Post a Comment