Profile question

[RedHair]

If the Profile provider is db, since ASP.NET will create profile class
to append to HttpContext object for each request , it means there is
a db access for each request? if so, does it cause performance issue?

Thanks

 

[Scott Allen]

There provider hits the database only if the page uses a profile
property (a lazy load pattern). I wrote a bit about the topic here:
http://odetocode.com/Blogs/scott/archive/2005/12/28/2661.aspx.


For most sites, the database hit isn't going to be an issue.

 

[RedHair]

Thank you, Scott.
Is it possible to read profile properties once from db per-user base then
store them into cookie to avoid db hit for future page requests?

 

[Scott Allen]

Thank you, Scott.
Is it possible to read profile properties once from db per-user base then
store them into cookie to avoid db hit for future page requests?

There is nothing built-in to do this, but you could write your own
provider. There are some whitepapers to help with out:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspp/html/ASPNETProvMod_Prt5.asp