I am using a separate database for the role based security files and when I deploy for the first time it automatically creates the physical database files in a default folder. We have customers that implement policies for the physical location of database files. Is there any way to specify the folder location if the database does not exist? I basically use your standard deployment routines, which I have wrapped for customer use, so does your standard deployment routine currently support this?.

Tim

If you want to change the deployment path of the physical database files, the easiest thing is to change the default deployment path of SQL server. This is what I would recommend if at all possible.

However, if you still need to deploy the files to somewhere other than SQL Server's default path then, yes, you'll need to change the DDT source code as Ben described to enable that functionality.

Sorry, it is not possible for us, as we have to follow our customer IT policy.







Change DDT source is the LAST step I would consider, as I don't want to worry any break if any strataframe upgrade. Therefore, I am looking for long term solution. I would like to request SF provide some way (such as make the method overriable) for us to override this behavour. Some more, ALL of our customers (900 customers) have this kind of requirement, it should be standard policy.



Beside, I also would like SF to make SF code more extendable in the sense, SF user could extend / override SF framework more by themselves. As SF framework really provide very robust RAD experience, however, when come to the time to extend/override default SF behavour, it is always restricted as most of the methods are marked private.



Please advice. Thank you