Ben Spead · May 17, 2021 go to post

The nice advantage of storing them in the DB is that is makes the following easier:

- refreshing earlier environments for testing
- mirroring the file contents
- encryption
- simpler consistent backups

However, if you're talking about hundreds of GBs of data, then you can run into issues which you should weigh against the above:

- journaling volume
- .dat size
- .dat restore time

One way to help mitigate the above for larger volume file management is to map the classes that are storing the the stream properties into their own .DAT so they can be managed separately from other application data, and then you can even use subscript level mapping to cap the size of the file .DATs.  

Hope that helps

Ben Spead · Apr 27, 2021 go to post

Congrats!!!  Well deserved:)  Thank you all for your contributions!! 

Ben Spead · Apr 21, 2021 go to post

Thank you for publishing!!

I am curious ... did you start with one of the existing open source Git hooks for ObjectScript or did you start from scratch with this project?

Ben Spead · Apr 19, 2021 go to post

Great article @John Murray!  We automatically set this global in our environment configuration logic (as well as set notify the user as to the application and environment type in ZWELCOME) whenever we run our customized instance configuration script.  Very helpful to make the intention of the environment clear whenever you are in the SMP!

Ben Spead · Apr 19, 2021 go to post

Are you asking how to check a global to see if the system is Dev/Test/Production as per the "System Mode" dropdown in the "Memory and Startup" page in the SMP?

 

If so, then this is stored in the following global:

^%SYS("SystemMode")

It should have values like "DEVELOPMENT", "TEST" and "LIVE"

Ben Spead · Apr 6, 2021 go to post

Thanks for getting the work out Tracey!  If any users have any questions, please feel free to ask.  

Ben Spead · Mar 29, 2021 go to post

Very interesting Evgeny!  Just curious what the motivating case is for this?  

Ben Spead · Mar 29, 2021 go to post

Thanks!  I see you updated the article with links.  Very helpful :)

Ben Spead · Mar 26, 2021 go to post

Very exciting!!  Congratulations to all involved in getting these out the door :)

Ben Spead · Mar 25, 2021 go to post

Terrific article Tim - thank you for writing it!  I have bookmarked it for future reference :)

Ben Spead · Mar 25, 2021 go to post

What is the system to use for enabling/disabling System Items?

Ben Spead · Mar 17, 2021 go to post

Phil - I wasn't suggesting that you use the Ens.Deployment.Utils but rather the Studio.Project utilities.  This will allow you to put in any specific classes that you wish to include (including the Production definition which should include all the pointers to the new BOs, BPs, and BSs) so that you can cherry pick what goes into your next environment.  I am not familiar with the Ens.Deployment.Utils so I can't compare the approproaches

Ben Spead · Mar 16, 2021 go to post

You could add the specific pieces you wish to deploy to a Project in Studio and export that project and then import it where you need it.