| Author |
 Topic  |
|
|
Mike Reynolds
2 Posts |
 Posted - 12/21/2005 : 05:38:13
|
I create new databases with DBGhost using XML/Scripts. However, although the logical name of the new database is fine, the naming of the resulting MDF and LDF files is strange.
For example, a new database with a logical database name of "Test":
When created in SQL Server Enterprise Manager the resulting MDF/LDF files will be; "Test_Data.mdf" and "Test_Log.ldf".
The DBGhost generated files wil be; "Test1.mdf" and "Test1.ldf".
How can I make sure that the Enterprise Manage naming convention is maintained?
The does not appear to be anything relevant in the DBGhost generated XML file(s)?
With thanks,
Mike Reynolds.
|
|
|
Mark Baekdal
86 Posts |
Posted - 12/22/2005 : 07:54:35
|
Unfortunately there's nothing you can do to change the behaviour of DB Ghost's way of creating database file names.
I'm intrigued to know why the names of the database files matter?
regards,
Mark Baekdal
http://www.dbghost.com
http://www.innovartis.co.uk
+44 (0)208 241 1762
Build, Comparison and Synchronization from Source Control = Database change management for SQL Server
|
 |
|
|
Mike Reynolds
2 Posts |
Posted - 12/23/2005 : 03:01:06
|
Mark, nothing of really great importance except that during development some members of the team like to take a copy of the test database files and attach them by hand in enterprise manager (working on a home/private PC).
Actually, a more important point is to be able to, not only set which SQL server the new database will be created, but also to be able to decide where the files will be created (directory path that is). I also can not see this in the XML file created by DBGhost, but perhaps I just missed it?
Although I have not looked too much at this problem yet, I am sure a work around can be found. (Such as creating the database through VB code and then using DBGhost to update/modify the new database with the relevant Tables, Views etc.)
Best regards.
quote:
Originally posted by Mark Baekdal
Unfortunately there's nothing you can do to change the behaviour of DB Ghost's way of creating database file names.
I'm intrigued to know why the names of the database files matter?
regards,
Mark Baekdal
http://www.dbghost.com
http://www.innovartis.co.uk
+44 (0)208 241 1762
Build, Comparison and Synchronization from Source Control = Database change management for SQL Server
|
|
|
|
Mark Baekdal
86 Posts |
Posted - 12/23/2005 : 03:22:03
|
Actually, a more important point is to be able to, not only set which SQL server the new database will be created, but also to be able to decide where the files will be created (directory path that is). I also can not see this in the XML file created by DBGhost, but perhaps I just missed it?
What you need to know/remember is that DB Ghost uses the target/template to use for all the properties of the database it creates. If you create a template for your individual purposes in the location you desire then you can achieve your end goal.
I've never encountered a situation where this is a problem as you can always get the files and the files remain small in general as the databases are just source code - they don't contain transactional business data that usually makes a database very large.
regards,
Mark Baekdal
http://www.dbghost.com
http://www.innovartis.co.uk
+44 (0)208 241 1762
Build, Comparison and Synchronization from Source Control = Database change management for SQL Server
|
|
|
|
Bradley
3 Posts |
Posted - 10/29/2007 : 09:51:40
|
I ran into a similar situation. We work in a highly regulated industry and every aspect of our software is looked at critically. This includes the name and location of the mdf/ldf files. The way I worked around this, is that I never use DBGhost to create a database. All our databases are created by a very small SQL file that merely created the database, but puts no tables or objects in it (except for one default, but that is a different issue.) Then all I create in DBGhost is an Update package, for that empty database, based on my source DB.
Probably not the "Right" way, but it solves the problem, and accomplishes what we need.
Hope this helps... |
|
|
| |
Topic |
|
|
|
MDF/LDF files naming conventions
