ISTech Support Forum - Better database concurrency

Welcome, Guest. Please Login.

	02/18/25 at 15:24:01 News: \| IS Tech Support \| Evo~ERP \| Evo Wiki \| Forum \|

ISTech Support Forum › Evo-ERP and DBA Classic › Suggestions for Updates

‹ Previous topic | Next topic ›

Pages: 1

Better database concurrency (Read 653 times)

kkmfg

Senior Member

Ghost of the code

Posts: 375
Gender: male

Better database concurrency
01/17/07 at 08:13:16

This would probably require a change away from my "favorite" database server (Pervasive) but I'm a glutton for punishment so I'll try anyway:

It's annoying that changing defaults tends to get denied because there are other users logged into the company. I really don't care who is logged into the company, I'd like to change the settings. These settings should immediately take effect for all new operations. It shouldn't be that hard to make it change the settings on the fly and have all programs run after that point use the new settings.

Collin
K & K Manufacturing, Inc

EvoERP Version 1-22-10 SP3
5 User Workgroup Pervasive 10

IP Logged

kevind Active Member I was more than willing to "pony up", how b'out U? Posts: 634 Gender:	Re: Better database concurrency Reply #1 - 01/17/07 at 09:28:31 I believe most of these denials are coded in the tas applications to protect us from ourselves. Having said that, I would like an Administrative option to turn off those denials so that I can change things that I know are not effected by others logged in.
Back to top	Kevin Damke Spectronics Corporation ISTECH 2004.1 7/26/13 SP1 - 20 user Evo-ERP Build 7/25/13 T7 -7i R6 - 3 user (Prev version was 2004.1 10/24/12) (All Patches Installed as of 7/26/13) Pervasive 2000i SP4 - Crystal Reports V10 IP Logged

kkmfg

Senior Member

Ghost of the code

Posts: 375
Gender: male

Re: Better database concurrency
Reply #2 - 01/17/07 at 10:56:49

That is probably true but changing most of the defaults will not cause any havoc for the logged in users. You can't even change the message to print on the bottom of sales orders while someone is logged in. That's only used by the sales order printing program and could EASILY be changed on the fly.

In reality I suppose it's not a huge deal but it is annoying and totally unnecessary.

Collin
K & K Manufacturing, Inc

EvoERP Version 1-22-10 SP3
5 User Workgroup Pervasive 10

IP Logged

NovaZyg

Administrator

When all else
fails.. Read the
instructions.

Posts: 789
Gender: male

Re: Better database concurrency
Reply #3 - 01/17/07 at 10:59:21

Bottom line, it is poor design. all the settings (DBA's that is) are located in two files. BKSYMSTR and BKYSMSTR.. and almost every program opens these files. So when you are trying to make a change to settings, if you lock the one and only record in the file, then everyone else would be locked out... this is the file contains info like next SO# WO# PO# check # etc... not something you want to mess with. That being said, a savvy user could look at the DBA source code and figure out what field it is they need to change and use maintain database to do so. but be quick, as that will also lock the record for as long as you have the file open.

Allen Landry
Evo~ERP

EvoERP and DBA Classic always Beta's of the Latest versions.

IP Logged

kkmfg

Senior Member

Ghost of the code

Posts: 375
Gender: male

Re: Better database concurrency
Reply #4 - 01/17/07 at 11:09:38

Hmm, well at least that makes sense. Let me guess, PervasiveSQL doesn't support updating a record that is locked... Like even PostgreSQL will let you do. And that is free. (I believe in Postgre that is called MVCC).

Is it possible to seperate all of the settings into different rows and use row level locks so that only users that are really affected can block you? Maybe it's not worth the time to do that though... Sad

Collin
K & K Manufacturing, Inc

EvoERP Version 1-22-10 SP3
5 User Workgroup Pervasive 10

IP Logged

kevind Active Member I was more than willing to "pony up", how b'out U? Posts: 634 Gender:	Re: Better database concurrency Reply #5 - 01/22/07 at 12:26:53 Allen, Are you saying that it would not be possible to show the current settings, allow a change to the field on the screen, re-read the record with a lock, apply the change and write the new record back? (quick read-modify-write)
Back to top	Kevin Damke Spectronics Corporation ISTECH 2004.1 7/26/13 SP1 - 20 user Evo-ERP Build 7/25/13 T7 -7i R6 - 3 user (Prev version was 2004.1 10/24/12) (All Patches Installed as of 7/26/13) Pervasive 2000i SP4 - Crystal Reports V10 IP Logged

NovaZyg

Administrator

When all else
fails.. Read the
instructions.

Posts: 789
Gender: male

Re: Better database concurrency
Reply #6 - 01/22/07 at 13:01:35

Kevin,

That is JIT locking (Just In Time) and we have done that to a number of places in the system already. That is how I have fixed most of the PO, SO, and Inventory locks. BUT I would not do that with these files, as all WO# and SO# , next checking numbers etc.. come from these files.. Lynn and I have talked about moving those numbers out of the BKSYMSTR table and into their own tables, but that is a big undertaking, for very little gain. We may still go there, it all depends on you the users, if you get enough support for this, then we will do it.

Allen Landry
Evo~ERP

EvoERP and DBA Classic always Beta's of the Latest versions.

IP Logged

kevind

Active Member

I was more than
willing to
"pony up",
how b'out U?

Posts: 634
Gender: male

Re: Better database concurrency
Reply #7 - 01/22/07 at 13:13:18

Allen,
... and we thank you for the JIT Locking!!!!!!
( http://www.istechforum.com/cgi-bin/YaBB.pl?board=General;action=display;num=1101 845646;start=2#2 )

I understand and appreciate any efforts to keep people from screwing things up.

As the system Administrator, I would like the ability to override the protection on the settings stored in these two files.

Kevin Damke
Spectronics Corporation
ISTECH 2004.1 7/26/13 SP1 - 20 user
Evo-ERP Build 7/25/13 T7 -7i R6 - 3 user
(Prev version was 2004.1 10/24/12)
(All Patches Installed as of 7/26/13)
Pervasive 2000i SP4 - Crystal Reports V10

IP Logged

Pages: 1

ISTech Support Forum › Evo-ERP and DBA Classic › Suggestions for Updates

‹ Previous topic | Next topic ›