StrataFrame Forum / StrataFrame Database Deployment Toolkit / Issues / Database Physical File Location / Latest Posts

RE: Database Physical File Location

Ben Chase — Wed, 14 Mar 2007 17:02:55 GMT

There is not a place within the DatabaseMigrator to allow you to specify the exact path for the file when it is created. The code looks like this:

If _SQLServer.Settings.DefaultFile.Length > 0 Then
lcReturn = _SQLServer.Settings.DefaultFile
Else
lcReturn = _SQLServer.Information.MasterDBPath
End If

The _SQLServer is a Microsoft.SqlServer.Management.Smo.Server object. The Settings.DefaultFile is the default location for the data set by the install of SQL Server. The Information.MasterDbPath is the path that you can specify within the server properties in SQL Server Management Studio. So, it always places the .mdf files within the default database location. If you need to change that, you'll need to change the source code. In the DatabaseMigrator class, it's either going to be the GetDataFilePath() method or the CreateSmoDataFile() method.

RE: Database Physical File Location

Tim Dol — Wed, 14 Mar 2007 13:44:42 GMT

I can't seem to find where to set the folder name to create the physical .dat file and transaction log file. Is there some place to do this in the mddeployprocess or do I have to modify the source code to do this.

Thanks

TIm

RE: Database Physical File Location

Ben Chase — Wed, 28 Feb 2007 14:47:51 GMT

Yes, when you create the database using SMO, if you specify the filename, you cannot specify it without also specifying the folder in which to create it. So, we use the server's properties to determine the default path setup by SQL Server and the user-specified path for the data. If the user path is specified, then it gets used, otherwise, the default path gets used.

Database Physical File Location

Tim Dol — Wed, 28 Feb 2007 10:02:29 GMT

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