Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...useless data in aspnet tables after update (311 -> 337)useless data in aspnet tables after update (311 -> 337)
Previous
 
Next
New Post
12/6/2006 5:56 AM
 

We are preparing an system update of a bigger dnn 311 based portal to dnn 337. The portal contains several child portals and users, working in the main portal and also in one or more child portals. 

While we were testing the update, we found in our eyes (perhaps we are wrong) some of the aspnet_tables contain lots of useless data (not needed anymore) after the update.

All data in the tables aspnet_applications, aspnet_users and aspnet_membership could be deleted, only keeping entries with new appid (appname: dotnetnuke).
Also the whole data in the tables aspnet_roles, aspnet_profiles and aspnet_userinroles could be deleted.

As written, perhaps we are wrong, but if not, in our eyes the update script should clean up this tables. Any ideas about that?

Regards,
Benjamin

 
New Post
12/6/2006 6:00 AM
 
AFAIK, old data in the aspnet tables is not deleted to help tackle possible upgrade problems. If your site upgraded ok, you could manually delete these records, if upgrading of accounts went wrong, you can always check what info should be there.... So this is by design

Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
12/6/2006 7:33 AM
 
sure, that is what we did. and the update looks fine at all. however in my eyes data, which is not needed anymore shoudl be deleted ... by design.
 
New Post
12/6/2006 8:34 AM
 

well.. like i said.. there are cases where upgrade of the aspnet tables are not completely succesfull. Keeping the "old" data will help in such cases...


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
12/6/2006 8:37 AM
 
for sure, yes. what, if an update was succesfull? why just not delete the data after the update?
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...useless data in aspnet tables after update (311 -> 337)useless data in aspnet tables after update (311 -> 337)


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out