Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 7 of 7 total
Thread Restart time setting
Thu, Nov 16 2006 2:57 PMPermanent Link

"Jose Eduardo Helminsky"
Tim

Sometimes, no matter what I do, I have to restart server to solve some
problems.
I think it is interesting if you can use the timer event at server side to
restart server automatically.

It will reset any variables, drop memory garbage and free *ALL* objects
created before.

Eduardo

Thu, Nov 16 2006 3:56 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Eduardo,

<< Sometimes, no matter what I do, I have to restart server to solve some
problems. I think it is interesting if you can use the timer event at server
side to restart server automatically. >>

If that's the case, then there's something seriously wrong.  Our database
server has been running for months upon months without a restart.
Specifically, what issues are you having ?  Are any of the client
applications multi-threaded ?  Are there any server-side procedures,
triggers, etc. coded into the database server ?  Finally, how many
concurrent users are on the database server ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Fri, Nov 17 2006 4:11 AMPermanent Link

"Jose Eduardo Helminsky"
Tim

The only thing I have in this customer is concurrent users. There are almost
50 users using a POS system.
The DBISAM Server is a stock version. There is no multithread applications
running against server, neither server-side procedures nor triggers.
Sometimes I have received an AV error in DBSRVR when I try to call
StartTransaction. This error is very rare.

Eduardo

Fri, Nov 17 2006 10:32 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Eduardo,

<< The only thing I have in this customer is concurrent users. There are
almost 50 users using a POS system.The DBISAM Server is a stock version.
There is no multithread applications running against server, neither
server-side procedures nor triggers. Sometimes I have received an AV error
in DBSRVR when I try to call StartTransaction. This error is very rare. >>

We've had some users that have a lot of heavy usage, concurrent users switch
from using the DBISAM memory manager to FastMM in the database server with
great success.  Once you start getting above 50 concurrent users on the
database server, the DBISAM memory manager can suffer from fragmentation a
bit and can cause the virtual memory manager to start getting out of memory
errors.

--
Tim Young
Elevate Software
www.elevatesoft.com

Fri, Nov 17 2006 12:41 PMPermanent Link

"Jose Eduardo Helminsky"
Tim

Ok, this make sense.
I will change DBISAMMM to FastMM and let you know about some new issues.

Thanks
Just waiting for 4.X and the new ElevateDB (I am very interesting on SQL/PSM
to programming at server side without compiling the server again and produce
different versions of it.

Eduardo

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> escreveu na
mensagem news:3278B31F-3BD2-420A-80A1-2F0C0D739FD8@news.elevatesoft.com...
> Eduardo,
>
> << The only thing I have in this customer is concurrent users. There are
> almost 50 users using a POS system.The DBISAM Server is a stock version.
> There is no multithread applications running against server, neither
> server-side procedures nor triggers. Sometimes I have received an AV error
> in DBSRVR when I try to call StartTransaction. This error is very rare. >>
>
> We've had some users that have a lot of heavy usage, concurrent users
> switch from using the DBISAM memory manager to FastMM in the database
> server with great success.  Once you start getting above 50 concurrent
> users on the database server, the DBISAM memory manager can suffer from
> fragmentation a bit and can cause the virtual memory manager to start
> getting out of memory errors.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Mon, Nov 20 2006 4:45 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Eduardo,

<< Just waiting for 4.X and the new ElevateDB (I am very interesting on
SQL/PSM to programming at server side without compiling the server again and
produce different versions of it. >>

Well, we deviated a bit from the SQL/PSM standard in terms of exceptions,
dynamic statement bindings, cursor handling, but it's easier and better than
the standard.  For example, here's an exception handling example:

BEGIN
  DECLARE stmt STATEMENT;

  PREPARE stmt FROM 'CREATE TEMPORARY TABLE Test Table
                    (
                    "FirstColumn" INTEGER,
                    "SecondColumn" VARCHAR(30),
                    "ThirdColumn" CLOB,
                    PRIMARY KEY ("FirstColumn")
                    )

                    DESCRIPTION ''Performance Test Table''';
  EXCEPTION
     IF ErrorCode=800 THEN
        RAISE;
     ELSE
        RAISE ERROR CODE 10000 MESSAGE 'This is a test error';
     END IF;
END

And here's an example of using a cursor to update every row in a table:

BEGIN
  DECLARE Test CURSOR FOR stmt;

  PREPARE stmt FROM 'SELECT * FROM biolife';

  OPEN Test;

  FETCH FIRST FROM Test;

  WHILE NOT EOF(Test) DO
     UPDATE Test SET Category='Shark';
     FETCH NEXT FROM Test;
  END WHILE;
END

--
Tim Young
Elevate Software
www.elevatesoft.com

Tue, Nov 21 2006 4:38 AMPermanent Link

"Jose Eduardo Helminsky"
Tim

I understand when you say "standard" but Oracle guys don´t think like that.
We need power do develop stored procedures, and at least for me, does not
matter if you deviate from standards. Just put the power on ElevateDB Server
and left standards from second topic. Of course if you can follow the
standards and put the power, that is the way but if not, you know how to get
away from this trouble.

Eduardo

Image