View Single Post
  #3 (permalink)  
Old August 6th, 2006, 04:34 AM
Imar's Avatar
Imar Imar is offline
Wrox Author
Points: 67,332, Level: 100
Points: 67,332, Level: 100 Points: 67,332, Level: 100 Points: 67,332, Level: 100
Activity: 100%
Activity: 100% Activity: 100% Activity: 100%
 
Join Date: Jun 2003
Location: Utrecht, Netherlands.
Posts: 16,231
Thanks: 66
Thanked 1,418 Times in 1,398 Posts
Default

Hi there,

First of all, when you run aspnet_regsql it does indeed create a lot of tables by default. However, if you run the tool from a command line, you can specify what features you want to support. Type aspnet_regsql /? for more info.

I don't think it's a good idea to work with SQL Express now if your intention is to switch to Oracle. I think you'll run into a lot of problems with incompatible code when you make the switch.

Writing your own provider is not that hard. And the main benefit of your own provider is that you can easily rewrite the code so it works with Oracle. Take a look here for some suggestions about creating your own provider:

http://Imar.Spaanjaars.Com/QuickDocId.aspx?quickdoc=380

I am not sure, but I wouldn't be surprised if there were already Oracle providers.

If you want to store some additional info besides the (default) user tables, maybe this helps:

http://weblogs.asp.net/scottgu/archi...18/427754.aspx

With this solution, you can use the standard Login features offered by .NET 2.0 and store additional info in the Profile object.

However, all of this will only work out of the box with a SQL Server database, not with Oracle.

Hope this helps,

Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results and Beginning Dreamweaver MX / MX 2004
Want to be my colleague? Then check out this post.
Reply With Quote