Icon ElevateDB 2.34 Released

Posted by Tim Young on Fri, Mar 26 2021
ElevateDB 2.34 is now available for download. If you're an existing customer, then you should be receiving an email shortly with download instructions.

The following are the new features in 2.34:
  • The job scheduling and execution has been improved in order to deal with jobs that experience errors. There is now a TEDBEngine ServerJobRetries property that allows you to specify how many times a job that experiences an error/exception will be retried before the job is disabled. There is also an ElevateDB Server setting called Server Job Retries that allows you to specify the same job execution parameter. You can use the ENABLE JOB statement to re-enable a job after it was disabled due to errors.


  • You can now use functions (in addition to procedures) with the CALL statement.
ElevateDB 2.34 also contains a couple of bug fixes, which are detailed here.


Tags: ElevateDB, New ReleasesPermanent Link

Comments Comments (10) You must be logged in to comment

Comment takoankosi said... Reply
There is also an ElevateDB Server setting called Server Job Retries that allows you to specify the same job execution parameter. https://basketballbros.org/

Comment Rebecca Greenwood said... Reply
I once faced a daunting issue with job failures in a previous project. Just like playing a Connections Game, each retry felt like navigating through a maze of potential pitfalls. Ultimately, adapting the approach led to a successful resolution. https://connectionsgamefree.com

Comment Bethany Bennett said... Reply
Awesome to see the new ElevateDB 2.34 release! Those job scheduling improvements sound super helpful, especially the retry mechanism – that'll definitely save some headaches. And enabling functions with the CALL statement opens up some neat possibilities. Always great to see continuous development. Makes me think of the dedicated effort some groups put in, like the Football Bros at https://footballbrosfree.com, always striving for excellence!

Comment Kaden ure said... Reply
Retries settings are a welcome addition for robust job handling. Think of it like Uno Online; when you make a mistake, you get a second chance! These retries provide that safety net, preventing job failure from derailing entire processes. https://unonline.io/

Comment Skinner said... Reply
That's a neat improvement! Reminds me of trying to have a good Omegle conversation. Sometimes you get disconnected or someone's being weird, and you just gotta hit "new chat" and try again, hoping the next one works out better. Glad there's a system in place now for jobs that have similar "bad luck"!https://omegleweb.io

Comment Wheeler said... Reply
That's a cool feature! Makes me think about Fnaf, actually. Imagine if the animatronics' programming glitched out less often because of something like this system. Less jumpscares because Freddy couldn't pathfind properly! Jokes aside, it's good to see robustness being built into the job scheduler.
https://fnafgamefree.com

Comment Morgan said... Reply
That's a neat feature! I wish Retro Bowl had something similar. It's frustrating when the game crashes mid-season. Maybe instead of retries, it could auto-save more frequently or offer a rewind option for a lost game. Would be a great quality of life improvement for those unexpected glitches!
https://retrobowlfree.com

Comment Daniels said... Reply
That's a great improvement! Reminds me of how frustrating Drive Mad can be sometimes. When a level's physics glitches and you wipe out repeatedly, it's tempting to just give up. Having the game automatically retry levels after a minor crash would be amazing and prevent that from happening, so this retry setup sounds really useful.
https://drivemadfree.com

Comment iogames said... Reply
The new TEDBEngine ServerJobRetries property is a valuable addition, enhancing job management by allowing retries for failed jobs. The ability to use functions with the CALL statement is also a great improvement. For more insights and updates on ElevateDB, check out  https://www.thevault.wiki  for comprehensive resources and discussions!

Comment Daniel Bird said... Reply
It's like the system is playing its own version of Crossy Road with my patience! I swear. Back in college, my database import script kept crashing halfway through. Turns out, a single rogue character in the input data was the culprit. I wish I had a retry mechanism back then, I would have saved hours.
https://crossyroadfree.com

Image