| Author |
 Topic  |
|
|
Seth
3 Posts |
 Posted - 03/23/2009 : 09:15:57
|
The changes to DB Ghost to allow relative paths is very helpful in allowing all of our team members to use a single configuration file made available via our source control system. We are now, however, encountering a new sticking point.
If each developer is using a different database, they each need to provide separate database connection information to DB Ghost. This means that the settings file in source control should not store database connection information. We can edit the setting file to remove the connection information, but we lose the ability to use the "skip wizard" feature. Is there some way that DB Ghost could prompt for connection info if it was missing when the "process" button is clicked?
|
|
|
Mark Baekdal
86 Posts |
|
|
Seth
3 Posts |
Posted - 04/01/2009 : 09:08:20
|
We would greatly appreciate it if your team would consider adding something like this in a future version.
When following best practices of each developer is working within his own sandbox and placing all build dependencies under source control (which includes the DG Ghost configuration file), this behavior throws a bit of a speed bump and risk of unintended changes in the build process.
Thanks. |
 |
|
|
leachm
124 Posts |
Posted - 04/01/2009 : 09:16:40
|
Hi Seth,
Can't your developers just use the same database name for their local instances? That seems like a really simple, immediately implementable, permanent solution...
regards,
Malcolm Leach
www.innovartis.co.uk
DB Ghost Build, Compare and Synchronize = Change Management for SQL Server |
Edited by - leachm on 04/01/2009 09:17:05 |
|
|
|
Thorin
5 Posts |
Posted - 04/01/2009 : 17:07:19
|
It's possible Seth's developers don't have local instances of the database, but rather separate instances on a central database server. If that is the case, they would need to provide at least a separate database name when connecting to said databases.
Although, thinking about it, said central database server could be configured to have each user's default database be set to their own database.
Anyway, just thought I'd mention a case where Seth's request might make sense. |
|
|
| |
Topic |
|
|
|
Prompt for database connection info
