I’m wondering if KDB has WORM (Write once and read many) function. We are trying to see if KDB can be used for some reporting purposes.  We would like to have some table read/write and some table read only after write. Is that possible?

I have downloaded the on-demand 64bit version of kdb. I launch the kdb+ as follows: C:\q\w64\q.exe Then I create a simple table as follows: t:([]k: 1 2 1; v:`A`B`C) Then when I try to query it using the SQL interface as follows, I get the error: .s.e"SELECT * FROM t" '.s.e [3] .s.e"SELECT * FROM t" The command is not recognized. How do I make it work?

We currently run straight kdb 4.0 and want to test how our system  will run on kx insights. We desire to test on an "on prem" server - if we just test kdb 4.1 on an on prem server will the behavior be identical to a standard kx insights installed system?

We are storing data in S3 bucket. While we are able to load most of the tables, whenever there is a column of the type list or string, the table couldn't load properly. When the column is a string say OrderID, it will have two files ID and ID#. when loading data locally it works ok, but it will complain about ID## when loading from s3. Does anyone know how to resolve this? 

We've using the KX insight on AWS cloud. When we are trying to set up the caching for HDB, it couldnt find kxreaper. Wondering what would be the right way to set it up?