Need advice about using ASP.NET Profile Provider

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I realize that ASP.NET profile provider is used to create a strongly typed
storage of data that can be used like Session variables but can survive
beyond sessions.

In my ASP.NET 2.0 application, I am thinking of using the ASP.NET profile
provider and its the binary storage capability to store a lot of my user's
custom variables versus rolling my own object storage and access in a
database.

Are there any limits or warnings I should be aware of when before relying on
Profile Provider versus rolling my own database storage and access?
 
AFIK one word comes to mind: performance. The use of the Profile does not
normalize data which trades ease of use for what can easily become
considerable impact on performance. That's my experience so far...

<%= Clinton Gallagher
 
Makes sense.

If I am storing 100 items in their profile, when are the items read? Are
all of them read upon first Load? Upon each call to Profile.NameOfVariable?
 
I'm not excatly sure about this yet. I thought I read that the data is
loaded on the first request. More needs to be known about Profile
performance that's for sure. Since its not normalized I think its going to
be correct to assume that its an all or nothing retrieval process.

<%= Clinton Gallagher
 
Thanks for your help.

Cause I was thinking, for those single non repeatable (row) options you need
to save, normalization doesn't buy you anyting so retieving it as a profile
is no issue. Providing the data is not required for OLAP and so on..
 
Back
Top