@Andrew Barber - welcome to the community!

The links above were from out HealthShare documentation which is protected, however the content is identical in our InterSystems IRIS documentation which anyone can access.  Here are the pages shared by @Stephen Canzano but from our open docs:

https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=RSQL_createview

https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=RSQL_createtable

https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=RSQL_createfunction

https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=RSQL_createquery

Basically, you can do everything in InterSystems IRIS that you can in traditional relational DBs but you get object-oriented access thrown in as well.  So classes and tables are two views on the same persistence.  I suggest the following primers to help you start getting your head wrapped around it:

https://community.intersystems.com/post/classes-tables-and-globals-how-…

https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cl… (see the table comparing Object vs SQL concepts)

And a deeper dive into how it all works together:

https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cl…

(or from the OO lense: https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cl…) 

Hope that helps get you started.  Keep asking questions - the Community is a great place to learn!

most welcome :)  

@Vitaliy Serdtsev  - you make a fair point about downloading the full Eval kit just for a few pieces of it ... unfortunately that is the only distribution mechanism that I know of currently available for non-supported customers.

Thank you for all the time you've spent over the years helping to find ways to make Caché more robust!!  It sounds like you've been able to identify quite a few areas of improvement.  There was significant effort put into streamlining things and solving known issues in the rebirth of Caché as InterSystems IRIS.  You might find it interesting to download the Community Edition (IRIS version of the SU kit but much more powerful with fewer restrictions) and see if the bugs you reported are still present there or not.  What do you think about that approach?

I got clarification that we still create an SU version of Caché which is available in the WRC because some of our large partners/APs rely on it for people to learn on (which makes sense).  Obviously we won't want new prospects playing with it, which is why it is no longer publicly available and instead we provide the InterSystems IRIS Community Edition.

you are most welcome - Welcome to the InterSystems Developer Community!

What you heard from the WRC was in error - 2018.1.6 has been planned for over a year.  It definitely fixes known bugs (otherwise why release a maintenance release?  ;) )

@Vitaliy Serdtsev - you could download the Community Edition of InterSystems IRIS from evaluation.InterSystems.com and just install Studio from that if you wish.  Also, is there a reason you want the SingleUser version of Caché rather than the InterSystems IRIS Community Edition (which is freely available to everyone)?  

Thanks for the additional use-case :)

Good point Robert!

@Evgeny Shvarov  - you cannot use "!<cmd line>" from the Output window of Studio.  It is often very helpful to run a command from the context of a serverside Caché/InterSystems IRIS process which you can do via the Output Window with the above command, but not with "!":

!whoami
whoami - Error <SYNTAX>

Kill stream Set sc = ##class(%Studio.SourceControl.ISC).RunCmd("whoami",.stream,,1) w ! do stream.OutputToDevice() If 'sc { Write $System.Status.GetErrorText(sc) }
CMD: whoami
irisusr

Again, this is particularly useful when running server-side source control commands (if you need to debug or augment hooks)