-
Kim Lombard
- PowerBuilder
- Thursday, 27 March 2025 01:55 PM UTC
Hello again. I have a working but not what I consider "runnable" application that I just migrated from PB 10 --> PB 22 R3. My users says it's unusable, which I agree. It is a mission critical business app, which I explained in some detail in another post. It does pretty basic stuff from a IT perspective. These are the issues.
PB 10.2 with 1996 - 1999 ish PFC
Load for initial window with treeview time Fast, very fast. Always open. Basically its the main menu with Right Click submenus based on the node in the TV_1 object. Load time < 10 sec. even during peak demand hours.
Query time Fast. POP, like right now.
Problems with Locking / Blocking - frequent and many since January when our Azure servers were updated.
Number of client WAH laptops that do "actual work" - < 10
Number of client WAH laptops that a lookie-loos (for system demos to big wigs, criticizing that its not modern look and feel, evaluating the work of the worked bees > 10 but never at the same time and only when its close to a deadline. You get the picture
Back end connection / servers / connection string - one connection that can switch from DEV --> QA --> Prod and pipe LOTs of data
Pipe performance. Acceptable, not a problem. if it works, don't fix it.
Current Multi user capabilities: Since Jan, not much. Can't copy a large case file and deploy at the same time as another user. Spinning, locks / blocking all over the place on SSMS activity monitor. Having to move to a CPC Cloud VM co-located with Server to "get the work done"
Current Transaction supported basically through PFC via SQLCA.
PB 22 V3 with same PFC
Load time for Main Treeview, same functionality SLOW, VERY SLOW. Greater that a minute.
Query / Update / Insert times. Brutally slow. Not usable. Search times. OK.
Problems with Locking / Blocking - TBD. the subject of this post and line of inquiry
Number of clients will be the same.
Number of connections will be the same. but only a single connection for each WAH work station
Back end connection to servers will go from OLE DB --> MSOLEDBSQL SQL Server v19.? with "UseHwnd=No",SQLCA.DBParm = " OJSyntax='PB' "
Pipe performance TBD
Current Multi user capabilities: Required, purpose of the migration from PB 10 --> PB 22. Probably max 20 users.
Problems with Locking / Blocking - TBD. I can emulate three sessions. One from my WAH system, two on the VM.
THIS HAS TO WORK FLAWLESSLY.
Need to updgrade from PFC 1999ish to PFC 22. Topic of this question.
--------------------------
Now my questions and current observations are as follows:
1) the system is "smallish" < 10,000 lines of code.
2) the code running creating the above comments is pretty much identical with minor tweaks
3) the usage of PFC 99 is small. Just Transaction nvuo_transaction, nvuo_visual_pipeline, parsetostring function. that's pretty much it. Oh, maybe printer stuff.
4) I'm redoing some of the system flow to delay initial "pull" from the DB, changing DDDW to be a search form instead of 10k rows going in the the list. I'm adding (nolocks) to the SQL against LARGE Tables. I'm changing some of the "slower" embedded SQL to SPROCS on the server. Some performance improvements, but not enough
5) Q1: Is it worth upgrading the PFC? We have "execute immediate" on the Begin Trans, Commit, Rollback, etc. How does this work for PB22?
6) Q2: If I do a side by side comparison of the PFC for transactions - it's that basically the same as upgrading from PFC 99 to PFC 22?
7) Q3: Should I "try" NO PFC Transaction handlings and "let powerbuilder handle it".. I know it depends on business case. The last migration that I did was on a similiar APP written in PB 10 --> PB 22 and I dropped the transaction logic because the users never work on the same Document at the same time (hence it's not required to lock the table / row). It runs GREAT on PB22.
8) Q4: Does PB 22 default transactional processing really work with large tables but small number of users? I need to avoid deadlocks at any cost and avoid rollbacks, if possible.
9) Q5: What are the drawbacks to using pfc_of_transaction logic from of_begintran, of_commit, of_rollback of_rollback logic? If there are nested transactions is that OK?
10) Q6: Should I take the time to setup the Adventure Works test DB on my Azure server and test out these scenarios? Or would that possible lead to "false positive" findings. Remember prior to Azure problems, this was a smoking fast, accurate, low maintenace app for 25 years. Very little code changed. It has been run on Sybase servers (era 2000) SQL servers 2008 up thru 2019. AWS SQL for a couple of years then move to on prem Azure.
My conclusion is leaning towards upgrading to PFC 22, but I'm been advised that might be a heavy lift, which I'm pretty sure my company my not approve. Also, I'm a little concerned about the hugh size of PFC 22. I think I saw a 330 page pdf?
Thank you in advance.
I'm sorry for the long read. But I'm looking for guidance for the correct solution.
I know I probably should hire a consultant to evaluate and propose solutions to these problems. BUT, for now It's my problem. I can fix it. I did it last year. If I recommend to bring in outside help, I've probably talked myself out of a job and a solution that is a year or two away.
TY
Kim
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.