April 1, 2010 at 6:33 pm
Hello readers,
I am starting a new web based application using C# (ASP.NET), and have been looking at the data model that is given to us by our friends at Microsoft. one of my major concerns is the data model will not be able to handel hundreds of thousands of members and related records. Why do I say this?
1.) The use of a clustered primary key, not to mention it is a guid. WHY?????
2.) I question the security of the password storage mechanisms used. I see hashed and encrypted, however with the use of a machinekey stored in the web.config file.
Thoughts please....
April 1, 2010 at 7:23 pm
Use the model as a template. Nothing says you can't make changes, such as changing the primary key to a nonclustered index and making something else that is more appropriate the clustered index.
April 2, 2010 at 8:29 am
james.arceri (4/1/2010)
Hello readers,I am starting a new web based application using C# (ASP.NET), and have been looking at the data model that is given to us by our friends at Microsoft. one of my major concerns is the data model will not be able to handel hundreds of thousands of members and related records. Why do I say this?
1.) The use of a clustered primary key, not to mention it is a guid. WHY?????
2.) I question the security of the password storage mechanisms used. I see hashed and encrypted, however with the use of a machinekey stored in the web.config file.
Thoughts please....
I have not seen scalability or security issues with the membership database because you can run the wizard with custom option on a database you created.
Kind regards,
Gift Peddie
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply