I once separated one Ensemble database (with code and data) into two databases (one db for code, one db for data) on a running system.

It was not difficult actually:

1. Exported code from one database
2. Created new database.
3. Imported code into new database.
4. In a namespace switched code database from old database to a newly created one.
5. Deleted classes from old database.

But in my situation the code itself didn't change.

You're calling an Operation, right?

Operations can be called in async mode.

Make the call async and add wait activity?

Another check. Properties can't be SQL reserved words. I often name properties "Date", etc. only to forget that they can't be used in SQL as is only quoted, so I need to go to Class view and rename them to something else.

The main check we need is parametrization. SQL should not be concattenated from user input, but user input should be passed as an argument.

Well, what do you want to do with that list? Depending on your use case, the solution may differ.

For example to get a list of dashboards execute this query:

SELECT *
FROM %DeepSee_Dashboard.Definition

And to get a list of Pivots execute this one:

SELECT *
FROM %DeepSee_Dashboard.Pivot

And in MDX2JSON project I need to get a list of dashboards visible to the current user.  I use custom result set for that (because user may have access to dashes but not to SQL).

And Tuesday, April 23rd at 11am EDT we would be running an English version of the webinar.

Register here.

Great!

Here's zip archive/unarchive support. Maybe you can unite these two projects?

If it's possible restart the DR Mirror. WIJ should be recreated on startup.

Or a Skype group.

Right after you get this error, what's in your ^||isc.debug global?

zw ^||isc.debug

Can you try restarting the instance?

CSP absolutely should work.

Also check this post about clearing cached elements from webserver.

I never use return unless I really do want to exit from the method while inside some inner loop. So mainly I use quit.

You can separate a file into structured data using Virtual Document API.

To import HL7 into Ensemble please refer to these guides.

Generally it could look like this: HL7 → Virtual Document → Persistent storage → SQL GateWay → MS SQL Server.

-Creating SSL/TLS configurations in S1's Healthshare portal (also tried with a %SuperServer... but where and how could I use them ? I haven't found it)

Your SSL configuration should be called %SuperServer. Currently it's called AccDirSsl. You need to create new/rename existing configuration to %SuperServer.

Also, can you show a screen from the Portal’s System-wide Security Parameters page (System Administration > Security > System Security > System-wide Security Parameters)? For the Superserver SSL/TLS Support choice, you should select Enabled (not Required).

Also does HS OS user has access to C:\chr11614pem? I'd try to copy certificates/keys to HS temp directory and modify paths in config accordingly.

From docs. RETURN and QUIT differ when issued from within a FOR, DO WHILE, or WHILE flow-of-control structure, or a TRY or CATCH block.

• You can use RETURN to terminate execution of a routine at any point, including from within a FOR, DO WHILE, or WHILE loop or nested loop structure. RETURN always exits the current routine, returning to the calling routine or terminating the program if there is no calling routine. RETURN always behaves the same, regardless of whether it is issued from within a code block. This includes a TRY block or a CATCH block.
• In contrast, QUIT exits only the current structure when issued from within a FOR loop, a DO WHILE loop, a WHILE loop, or a TRY or CATCH block. QUIT exits the structure block and continues execution of the current routine with the next command outside of that structure block. QUIT exits the current routine when issued outside of a block structure or from within an IF, ELSEIF, or ELSE code block.

Note that return and quit are not equal.