Thanks for your message and sorry for the delay in replying.
While it is technically possible to use a shared database with ReadyRoll, we do typically recommend that each developer have their own copy of the database. This is because, as ReadyRoll uses a connected style of development, it is possible that two developers working on new changes in parallel may cause changes to be duplicated in source control. Sorry about that.
Do you mind if I ask whether there are any specific challenges with your database environment that make per-developer environments unfeasible? (e.g. size of database, complexity with reproducing environment setup, etc)
Jeff Clark
Posts: 14
Comments
Thanks for your message and sorry for the delay in replying.
While it is technically possible to use a shared database with ReadyRoll, we do typically recommend that each developer have their own copy of the database. This is because, as ReadyRoll uses a connected style of development, it is possible that two developers working on new changes in parallel may cause changes to be duplicated in source control. Sorry about that.
Do you mind if I ask whether there are any specific challenges with your database environment that make per-developer environments unfeasible? (e.g. size of database, complexity with reproducing environment setup, etc)
Many thanks
Product Manager
Redgate Software