My company had a website where we manage our timesheets which is developed in ASP.NET 2.0. Recently we made a decision to use LDAP Authentication instead of using the SQL Membership that we used previously. Now this is generating all sorts of problems since the membership data is spread along some of the most important tables with GUIDs FKs on some tables that rely on aspnet_Users.
In terms of authentication we don't have any problems but we want to drop every table and column that references anything related to the SQL Membership. I haven't been able to do this so far since I need to drop the asp_* tables first.
I've tried aspnet_regsql.exe (it fails), I've tried the Web Administration tool (I was able to delete some data but not everything) and I still need to delete all these Membership related data.
Can anyone point out how can I achieve the intended outcome? I'm really lost here..
Now, if you have data in say an "orders" table that references a user that placed the order (and have a relationship between your membership user table and the orders table) this massive drop statement will fail - how are you accounting for updating your current data attributed to users to your new user store?
Found this copied from https://gist.github.com/dmorrison/942148