I had asked this in another thread, but thought better of it and am starting a new one.

I want to have the DNN installer run a SQL script(s) against a database other than the DNN database (an application db, to be precise).  Is there a way for the user to provide the database name as an install parameter, and access that parameter from the script?

Alternatively, is there a way to get the DNN database name at install time programmatically from within the SQL script?  We could then use that to determine the application db name, because we use a uniform naming convention,  (e.g. if the DNN database is called foo_dnn, we know the application database will be foo_data).

Thanks in advance.

Kevin

Chris,

Thanks for the reply but your alternative suggestion left me confused.  If the IUpgradeable implementation in my module won't be run until after the module is installed, how could I possibly use it to fetch the database name for my SQL script?  The script will have already run at that point.

Can you please point me to documentation on IUpgradeable and its use?

Thanks,

Kevin