I remember reading an answer to parts of the question that I'm about to pose sometime last year or early this year and would really appreciate it if somebody could either copy it to me or answer these questions from scratch.

How does the backend database handle the migration of forms when the production server already contains data. For example, if you are adding a new field to an existing form, does the database make a copy of the form and add the field then overwrite the original? If this is the way that it occurs, what happens if you haven't locked users out whilst making the change - how are the updates that were made to records in the original handled when the 'new' form is copied back?

Likewise, what happens when fields are deleted?

Remedy recommends that you switch MPSO off if you're in a UNIX environment for performance reasons. How are the changes migrated from server to server if you are in an NT environment or if you don't switch MPSO off?

If you use DSO, do you need to switch off updates and update both (all) DSO servers simultaneously or can you make changes to one server at a time. How will updates be handled if a record contains data in a new field on one server but that field doesn't exist on the target server?


I know that I've asked a lot of questions and I hope that I've explained my questions well enough. I would appreciate it if someone could enlighten me how Remedy makes changes to the database structure and how workflow elements are added.

Thanks in advance,

Dave.


Dave Edney
Praxa Limited - A ManTech International Company

-----------------------------------------------------
Get free email from CMP at http://www.cmpnetmail.com/

To Unsubscribe send e-mail to:
body of text is: unsubscribe arslist