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

HomeHomeDevelopment and...Development and...SQL and SQL Ser...SQL and SQL Ser...Migration of ASPNET dbo databases Migration of ASPNET dbo databases
Previous
 
Next
New Post
11/20/2011 6:46 AM
 
Is there a way to migrate the dbo.aspnet_* databases from 1 application to another. I have tried but when I do I get a database error on the applicationId field. I have a user database with over 1500 users and I do not want to have them all re-register in the new application. Any suggestions?
 
New Post
11/25/2011 3:23 PM
 
Tried it, failed, took more time than it was worth, decided to make users do their own.
 
New Post
11/26/2011 5:27 AM
 
what do you mean by migrate, would you mind to be more specific on your use case, please.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
8/5/2013 10:28 AM
 

I was going to start a new thread for my question, but I think what I am trying to accomplish is basically what the OP was trying to do here.

We have an existing Users database (standard db created from a MVC .NET app/SqlMembershipProvider, has all the aspnet_* tables) and we want to use it for a new DNN site. Is this possible, and if so, can someone point me in the right direction?

What I've tried so far is to install DNN to a new db. Then, edit the web.config for the site to add a connection string to my Users db and have the DNN web.config point to my conn string for the <AspNetSqlMembershipProvider> element, modify the <machineKey> element to match my other app's (the app that the Users db is a part of), and changed the "applicationName" to match what is referenced in the Users db. This has kind of worked, as any new users that are registered appear in my Users db (aspnet_Users, for instance), but I can't login with any new or existing users.

So, any help would be greatly appreciated. Thank you!

 

Adam

 
New Post
8/5/2013 9:54 PM
 
we actually added a setting (InstallMemberRole) for this when we first moved to using the Microsoft memberrole setup in DotNetNuke 3, as we imagined that this could be a common request - however it never really caught on and I can't honestly remember someone trying the setup in years, but it may be worth you having a go. To try it first ensure you have a safe copy of your existing site database. Now, create an IIS website with an install version of DNN in it - before installing, edit the web.config and point both connection strings to the database with the aspnet_* tables, and also ensure that you set InstallMemberRole to false - in theory when you do the install it will skip the part where we build the aspnet_* tables but perform the rest of the install as normal. I'd be interested in knowing if this works as I had a quick look at the code and didn't notice any user table imports, but perhaps I missed them

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeDevelopment and...Development and...SQL and SQL Ser...SQL and SQL Ser...Migration of ASPNET dbo databases Migration of ASPNET dbo databases


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