Recent content by ron

  1. ron

    Question Changing triggers.

    Thank you all for your contributions. I have to conclude that my plan to change the trigger code "in mid flight" was simply flawed. I will have to move to a different method.
  2. ron

    Question Changing triggers.

    11.7.4 on Linux Hi DBAs, I'm testing an addition to the system that uses write and delete triggers on a selection of tables. The triggers exist on a Linux server and four AppServers. I was hoping to be able to "switch-on" the triggers at an exact moment. I thought of a few different ways...
  3. ron

    Question Direct connect vs client/server.

    Thank you Cecil and Tom. I believe you have confirmed my understanding. I just wanted to be sure there was no "good reason" to use c/s that I was not aware of.
  4. ron

    Question Direct connect vs client/server.

    I should have explained a bit better. Yes, of course, a local user must use a client/server connection for getting at an AppServer. The situation I'm dealing with is users who simply access a DB using a character-based application. Ron.
  5. ron

    Question Direct connect vs client/server.

    11.7.4 on Linux Hello DBAs, Over a long period working with Progress, systems I have worked on have used a very straight-forward "rule" -- local users connect via "direct connect" (ie via shared memory) -- and remote users use client/server connections. However, in the system I work with now...
  6. ron

    Question Type 1 Storage Areas.

    OE 11.7.4 on Linux. As per best advice -- I have always set-up Storage Areas as Type 2 -- and appreciate the various reasons why Type 1 Areas should never be used (except of course for Area 6). However .... the system I look after is a package and like nearly all cases of using packaged...
  7. ron

    Question Transactions and Record Scope.

    Thank you Tom. I think what you have explained helps. I will pick my way through it and see if I can solve the problem. Ron.
  8. ron

    Question Transactions and Record Scope.

    Thank you Stefan -- I appreciate your help -- but it doesn't actually help. Tom and Dan have slides illustrating "strong" and "weak" scope -- but the slides are very simplistic. When I try to fit my logic around what they show I end-up in a mishmash that doesn't work. I will just have to play...
  9. ron

    Question Transactions and Record Scope.

    OE 11.7.4 on Linux. Although I've worked with Progress for a long time, I confess that my understanding of transactions and record scoping has many gaps. :confused: I have read (and re-read) presentations from Tom and Dan -- and I still have gaps. Here is a small test program: > cat...
  10. ron

    Question Copy replication trigger assignments.

    Yes, Rob, I think there are a number of ways this can be addressed -- but the big 'relief' is that the cause of the problem has been found .. it was really bugging me. (I'm sure you can imagine.)
  11. ron

    Question Copy replication trigger assignments.

    As I was explaining .... the replication system is working quite well -- except that it is slow. I checked the trigger code several times and could see no obvious reason for the problem. Each trigger deals with a different table, of course, but have exactly the same pattern. They: 1. Create...
  12. ron

    Question Copy replication trigger assignments.

    Tom and Rob -- thank you, your help is always very valuable! I deleted the post because I realised that it was my mistake -- I saw the compiler messages warning that some code would never be executed (of course!) -- but forgot that the compile script would deliberately NOT replace the existing...
  13. ron

    Question Copy replication trigger assignments.

    (Sorry - I've removed this until I do some more investigating.)
  14. ron

    Question Copy replication trigger assignments.

    Hi once again ... This project to replicate a particular set of tables is up-and-running. All works according to plan -- but the performance at peak times is "unspectacular". The problem is the trigger code. It was made to be as brief and uncomplicated as possible -- but I will have to...
Top