StrataFrame Forum

Migrating SF Projects

http://forum.strataframe.net/Topic15995.aspx

By Jason Seidell - 4/29/2008

I need to know how to migrate SF data from one database to another on a project level. I know I can backup the database and restore on another machine, but I want to be able to selectively copy projects from one machine to another for two reasons.



First, another developer and I both started using SF and just setup local DBs, and as I've learned this causes some problems when trying update each other's projects, and with two more developers soon joining the picture the idea of four different DB's that projects are tied to, and trying to manage permissions and apply SF updates unilaterally seems like too much work. So I want to merge all our SF projects into one SF DB.



Secondly, I would like to be able to copy the source code and the project DB files to a jump drive and work on code from home without having to VPN into work to get to the SF DB, and then when I'm done import the changes back into the work SF DB.



Maybe this has been explained somewhere else and I've just missed it. I've looked through the tables and it seems to complex for me to just blindly stab at trying to write an import/export program.



Any help is greatly appreciated.



PS. This post really applies to all the SF products, application framework, DDT, and role based security. Should this maybe placed in requested features forum instead??



Thanks,

Jason Seidell
By Trent L. Taylor - 4/29/2008

This is something that has been brought up more than once...and you won't like the answer Ermm  There is presently not a "merge" and if you read the docs and a number of other posts, this is why it is important to setup a central repository for projects, etc.  The reason that this is generally not an issue is because most development shops work from source control (which I highly recommend).  It is very risky to develop in a non-source controlled environment with .NET.  It can be done, but makes the sharing of solutions and projects difficult, but more importantly, you can never truly work properly in a multi-development environment.  So StrataFrame follows these rules and logic.

We do not plan, at present, to write a merge...this in and of itself could cause a lot of issues.  Future versions of SF will actually store the BO mappings within the project versus a SQL Server database.  But you will still have the DDT and RBS issues.

By Jason Seidell - 4/29/2008

Thanks (for the quick reply and the disappointment :cryingSmile, I was afraid that might be the answer. However not too bad since we only have a couple of projects that we will probably end up revamping anyways.



Does any of the source control (I'm guessing you are talking SourceSafe) integrate/enforce revision changes on the SF DB?? Or maybe the better question is how should that be handled??? (Or please give some best practices/software packages for source control with SF projects)



Jason
By Jason Seidell - 4/29/2008

However I do wish there was a way I could move all the source code and datafiles I need for a project into a single location so I could work on the project from another disconnected computer. And for backup purposes to capture everything for a project at a given point in time (ie. before a version update) without having to also snapshot the DB.
By Ivan George Borges - 4/29/2008

Hey Jason.

Not sure if you are already going to the class in July or not, but this is one of the subjects they go extensively about during the course.

Meanwhile, I guess your two best choices would be TeamSystem (and there is an MSDN subscription that comes with it, the Visual Studio Team System 2008 ones) and probably Vault (a cheaper choice, from SourceGear, www.sourcegear.com)

By Jason Seidell - 4/29/2008

Yeah, I'm real disappointed that the class in Febuary was cancelled, and unfortunately we are moving offices mid-July so it's shaky whether or not I'll be able to come.





Pinch
By Trent L. Taylor - 4/29/2008

Ivan is right...SourceSafe is really bad...don't even attempt to use it if you can keep from it.  But, it is better than nothing.  So if this is the ONLY choice you have, it is better than not using source control at all.  Ivan gave you the two best options for source control.