As part of our configuration management process with our offshore team, we often have to recreate our database schema in Oracle by dropping the schema owner and recreating that user as part of the create/import scripts delivered with a build. However, when trying to perform this task in our onshore Development, QA or UAT environments we are faced with an issue where the user could not be dropped due to the fact that said user was currently connected: DROP USER <user_to_drop> CASCADE *ERROR ......
In early 2006, we had a difficult bridge to cross as we were about to enter the Construction phase of our current project. Having 35+ developers building interdependent functional areas of the application, we needed to ensure the autonomy of each functional area, whilst maintaining linkage between shared components. Thus, having used branches in the past (quite successfully with Subversion, might I add,) we decided to leverage TFS branches to provide support for our concurrent development efforts. ......
It seems like the only time I have to myself is in airport lounges! As the post would suggest, I'm in the UK en route to Mumbai to visit my team, check up on things, enjoy some good Chicken Tikka... the usual drill.
Will be posting some TFS musings soon... hopefully, will have some goodies on SP1 and hardware migration.
Cheers!