StrataFrame Forum » StrataFrame Application Framework - V1 » Issues » Best practice for SF upgrade

Best practice for SF upgrade

jctscorpio — Sat, 18 Apr 2009 11:52:34 GMT

Since the SF db contains data specific to my source code, what needs to be done is order to do a SF upgrade without losing my data in SFSProjects, SFSUsers, etc.

The question might be stupid, but I really don't know what to best way to go.

RE: Best practice for SF upgrade

Trent L. Taylor — Sat, 18 Apr 2009 11:52:34 GMT

Thanks Greg...as Greg pointed out you ALWAYS want to update the databases with a new update. We are always careful to never hurt any data that you have created. At times we update the structures to add new features, etc.

RE: Best practice for SF upgrade

Greg McGuffey — Fri, 17 Apr 2009 21:56:02 GMT

yep, that would be the problem! You'd use this option if you have several SF installations using the same SF database. E.g. you have a team of SF developers all using the same StrataFrame db. In that case, the first one to update would update the SF database and the others could skip it.

RE: Best practice for SF upgrade

jctscorpio — Fri, 17 Apr 2009 21:16:36 GMT

You are right! I did the installation and now it works.

My problem (I think) was that I choose the 'Skip db deployment".

RE: Best practice for SF upgrade

Greg McGuffey — Fri, 17 Apr 2009 19:21:16 GMT

Typically, you just run the installer, point to the current, existing StrataFrame db (which has all the meta data for your projects) and run the install. The installer will update the db as necessary, leaving the data alone. I have no idea how many upgrades I've installed since I started with SF, but its been a lot (a dozen at least) and I've never had any issues with the SF database.