Hello,

I was trying to manually install DNN 5.1.1 to my shared hosting provider on Cheap-DomainRegistration.com.  Every time I got to the step where it installs the database scripts, the installer would error out.  I tried a few things and one of the things that finally worked was that instead of doing a "custom" install, I did a "typical" install and ran the database install as dbowner.  I suspect that it was running the scripts as dbowner that did the trick, but after all of the time that I spent installing DNN, I don't really want to go back and blow it away again, just in case I can't get it working again! 

Anyway, my question is what did I miss out on by doing a typical install as opposed to a custom install?

Regards,
John

Sebastian,

Thank you for your quick response.  My SQL Server account has as many permissions as they can give me without giving me the dbowner role.  I tried to grant it to myself, but I wasn't able to.  I have been granted the dbo schema, though. 

My install went through without any problems after I selected the "Typical" install.  Everything seems to be OK, but I was wondering what I missed out on by not going with the "Custom" install.  I'm a sys admin and whenever I do installs I usually go with the custom option because I know that sometimes you can select extra features that you might not get if you just go with a typical installation.  Is there some way to add any features that I might have missed out on?

Also, if my installation went through without any problems, is there some way to make sure that DNN is operating the correct way?  Or should I just assume that if the installation was successful that everything is fine?  I've never installed DNN in a hosting environment so I want to make sure that all my directory permissions are set correctly so that I don't start customizing and then find out that I've got to blow everything away   I know that there are myriad hosting providers out there and so it's impossible to give specific advice, so anything that you can give would be appreciated.

Thank you so much,
John

Jon,

if you selected "typical", AFAIK the file based access to database.mdf is used. if this is fine for you, you may continue w/o concern. If you would like to use attached database instead, you need to create the blank database manually and grant permission to the user, you specify in install wizard (custom mode) or connection string in web.config prior to the wizard if using typical mode.