The version of the documentation should be clearly displayed as there are differences between the respective versions (and not just in appearance).
The ordering of the sidebar is confusing to the point that I find it distracting.
The biggest question will be whether or not you have any sensitive information stored outside of Ensemble.
Please note with Caché/Ensemble Encryption there is no backdoor.
Write quote Hello World,
Dollar SYSTEM Dot Process
Dot Terminate(Pid)
The command $SYSTEM.SQL.DATEDIFF(outputFormat, start, end) is also quite useful for date arithmetic. It is a lot less picky about the format and a lot more powerful regarding the output.
When a language isn't strongly typed, I often test unexpected but possible types -- for example: Numbers or Strings instead of Dates or Booleans.
Other favorites:
As Jon Willeke suggested, I also use random data when possible (apart from the -1, 0, 1 defaults). The %Library.PopulateUtils class can be helpful for generating other preformatted random information.
ENSDEMO is not included in IRIS installations. However, it is available here: https://community.intersystems.com/post/install-ensdemo-iris.
This is an excellent article Murray! Thanks for putting it together. It was exactly what I needed for a conversation this morning.
Try ":sql" instead of
d $system.SQL.Shell()
It has been around for a few years.
Personally, I hesitate to use the alias capability lest I find myself in an environment without them!
Consider $System.OBJ.ExportToStream() and .LoadStream() to avoid local files with a change to the appropriate implicit namespace between.
I plan to delete this article the second that the version containing Stochastic Sampling is installed everywhere. In the meantime, I can think of a few customers that need alternatives.
Your SQL utilities are great and also available via Open Exchange.
Thanks for the feedback. We made sure that the product teams heard your perspective.
There is a button somewhere in the new rules editor for switching back to the old one. System wide, you can also disable the web application for the new rules editor.
We expect that the old ZEN based rules editor will be deprecated eventually. However, there are plenty of enhancements to the new in the pipeline based on valuable feedback like this.
Thanks, James! I knew it existed!
You should definitely avoid putting strange journal files in your local journal directory!
As Dmitry suggested, the Journal APIs will let you read the contents of a journal file. You can also use the existing Journal Profile utility for a general sense of which globals are most active in the file.
set path = ##class(%SYS.Journal.System).GetLastFileName() //example, use any journal file do ##class(%CSP.UI.System.OpenJournalPane).ComputeJournalProfile(path) zw:$ZV["Cach" ^CacheTemp.JournalProfile(path) zw:$ZV["IRIS" ^IRIS.Temp.JournalProfile(path)
+1 for %ResultSet being deprecated. I'd suggest using %SQL.Statement instead.
For your immediate question, it's a good practice to always check status codes.
set status = rs.Execute()
if ('status) {
write $SYSTEM.Status.GetErrorText(status)
}You also might find some information in Auditing if there is a security issue.
Great solution!
I compared the performance against querying %SYS.Journal.Records:List and found that using the objects is >10 times faster. Oddly, I couldn't execute the query via %SQL.Statement.
TestJournalFileNext 0.777671s
TestJournalResultSet: 10.972615s
I'm late to the party, but it looks like several had similar approaches.
60
ClassMethod IsValid(sAs%String) As%Boolean
{
f{sx="()",s=$CHANGE($TR(s,$TR(s,x)),x,"") q:s'[x} qs=""
}%request.Get("Top") will return the value which is stored in %request.Data("Top", 1).
If you want to iterate through all the values, I'd use @Ashok Kumar T 's solution or $ORDER on %request.Data.
Elijah has a great answer for this inquiry!
However, I would urge caution with this approach for production systems -- especially with large volumes of MessageHeaders + MessageBodies. Reading the entire corpus of messages into memory to find a particular value could have a significant impact on overall performance.
Two thoughts:
One question:
I expect transactions rolled back would be missing a TCOMMIT in the journal file. Walking the journal files and counting the TSTARTS vs TCOMMITS should give you a rough number. It could be off by the number of transactions that happened to be open at the start of the period. That error margin will vary significantly based on activity.
The start and completion should be included in messages.log.
I'd love to know more about your specific use case for using 32KB blocks for the database. In my experience, 8KB blocks are generally more adaptable unless you're exclusively working with atomic data elements that are that size or larger. IMHO, it's an instance wide consideration rather than only a database level consideration because allocating buffers of 32KB reserves a portion of the memory for blocks of that size.
Great post! This utility is highly underrated!
A few thoughts:
Great article! I like the code snippet for more advanced automation of managing transactions.
I often suggest this query to find transactions that are open longer than is suitable for operational stability.
SELECT *
FROM %SYS_Journal.Transaction_List()
WHEREDATEDIFF('s', StartTime, NOW()) > 60I thought about it a bit. There are additional possible explanations depending on deployment topology and journal purge settings:
@Stefano Cairoli reminded me of my vow to update this with the release of the stochastic estimator. @Sarah Matthews did a fantastic job building it!
I use the following to get the full query.
SELECT Location, RuntimeLocation, Statement->Statement FROM INFORMATION_SCHEMA.STATEMENT_LOCATIONS WHERE Location = ? OR RunTimeLocation = ?