Thanks everyone for your replies.  The data access layer I use is just too easy to give up!  I can do things like:
LinkRow row = new LinkRow();
row.Link = "www.bla.com";
row.Name = "bla.com";
ModuleDB db = new ModuleDB();
db.BeginTransaction();
db.LinkTable.Insert(link);
int id = link.LinkID;
db.CommitTransaction();
or
LinkRow[] rows = db.LinkTable.GetAsArray("moduleid=55", "DispalyOrder");
DataTable dt = db.LinkTable.GetAsDataTable("moduleid=55", "DispalyOrder");
or
db.StoredProcedures.ProcessExpiredLinks();

And the best part is that whenever I change the DB, I just regenerate the DAL with MyGeneration.

My layer is abstracted to support multiple server types easily.  However, it does not support multiple instances for different databases in the bin folder.
The user will have to overwrite the SQL version of the layer dll with an oracle version of the layer dll.  From what everyone is saying, this seems to be acceptable.

Thanks everyone!
Mike