Development work on hosted databases

[Audrey]

Hi,

I recently rolled out a Filemaker Pro 8 server (running on an OS X client machine). We have 6 databases being hosted there with none having more than 3 or 4 concurrent users. The databases are shut down and backed up nightly.

In the past when we were using the non-supported/non-recommended method of keeping our databases on a network volume (panther server) and running them from there, one of our programmers would make a copy of the database before she made revisions to it. Now that I’m hosting the databases properly, the programmer wants to know what she should for doing development work. She’s not comfortable with making changes and having them “stick” immediately.

Since fmpro server is running on an os x client, I have no plans of enabling file sharing on this machine. I wanted to poll the forum to find out what others do in a case like this.

Could anyone recommend links to admin/developers “best practices” that discuss this? I’ve already looked through the Filemaker Server Best Practices and didn’t see anything that applies.

Thanks in advance for any suggestions or recommendations.

-Audrey

Oh yeah, I forgot to mention the developer in question normally uses a PC.

[Wim Decorte]

Couple of choices:

1- make the changes "live" (would not recommend that)

2- make the changes in a backup copy, test until everything works fine and then redo the changes in the live system at night when no clients are connected

3- make the changes in a backup copy. At night put the changed backup copy on the server and import all data from the old live system

4- redesign the whole system to follow the "data separation" model

While #2 seems like a lot of work, it's my preferred method.

Edited January 19, 2006 by Guest
added #4

[xochi]

If you are able to have "down time" when users are not on the system, then making changes "Live" is not that bad of an option.

I'd suggest, however, that you consider the risk involved. If a change is minor (such as adding a field to a layout) you can probably do that during working hours. If it's more major (such as importing new data, re-desigining a table, etc.) you'll want to do that over a night /weekend.

Whatever you do, set up FM Server to make frequent backup copies. I have mine set to do hourly backups.

[Audrey]

She definitely isn’t interested in making “live” changes and I’d have to say I agree with her on that. So, I will likely end up suggesting method #2 or #3 depending on which one works better for her.

Thanks to both of you for your suggestions.