Okay normally I dont worry about it too much about security - I make regualr backups and figure if something happens I just go back a day change passwords etc. and I am done

My boss doesnt see it that way we are building out a DNN application that has to be fairly secure and I wont be able to go back and lose a day so what is the minimum roles/schema that a DNN install should have for the user that does the heavy lifting

I would like to create a role that handles it but not being a SQL Server 2005 person not sure I am choosing the right things

so I create a database that has all these roles avaialbe
aspnet_Membership_BasicAccess
aspnet_Membership_FullAccess
aspnet_Membership_ReportingAccess
aspnet_Profile_BasicAccess
aspnet_Profile_FullAccess
aspnet_Profile_ReportingAccess
aspnet_Roles_BasicAccess
aspnet_Roles_FullAccess
aspnet_Roles_ReportingAccess
db_accessadmin
db_backupoperator
db_datareader
db_datawriter
db_ddladmin
db_denydatareader
db_denydatawriter
db_owner
db_securityadmin

What ones should I have and what ones should I avoid - advice is appreciated

Yes I have read that and we have done a few of the things in there to help out security but it doenst really address what to do if you cant use Windows Auth in SQL server what roles should the user have to minimize damage someone might cause if they got hold of the username pass in the web.config

And when setting it up for Windows Auth what roles whould i set up the user for

Just some good solid advice would be nice