As in MS Word 2010, older versions than arcplan Enterprise 5 required shutting down via the menu, comparable to MS Word 2010 via “File” and “Exit”, in order to fully terminate the connections to the data base. If this is not done, objects may be locked in SAP or be unnecessarily blocked in other resources.
Since, however, this is no longer necessary as from arcplan Enterprise 5 and more recent, it is only a cosmetic process now.
Check whether IIS7 is installed
It's been ten years since SQL Server 2012 was brought out. Ten years, and soon it will be over again – at least as far as extended support is concerned. Before we talk about what this means and what our options are, I would like to take this opportunity to look back on these ten years: On aspects whose foundations were laid back then, and which are now standard in the database landscape, especially in the BI context.
When preparing reports, we repeatedly face the challenge of processing large quantities or complex information in a way which is clear and comprehensible for the report's consumers. Visualizations in the form of diagrams and charts can serve as an effective means here.
In this article, I would like to point out some important aspects which need to be taken into consideration when creating visualizations in reports, so as to achieve meaningful communication.
Long waiting periods are an irritation and a cause of much frustration when working with Tableau. In this case study, we look at how to get the performance of your Tableau data source back under control - even if you're using a live connection or a complex data model.
In case of arcplan applications, it is quite common that the relational data source from which the framework data for navigation, user administration, comments etc. are extracted are located on one server for the development, test and/or production version. This complicates the switch between these databases, as almost all metadata apart from the server connection is placed in the arcplan repository. In particular, this includes the database name, which now complicates the simple switch between various databases on the same server.
In arcplan, the individual selection constitutes a fixed list of elements which were selected by the developer. Up to arcplan Enterprise 6, a database query for an individual selection did not take place. Thus, this could be used for performance optimizations or for a pre-selection. However, customers frequently requested an add-on for updating the displayed texts. As a database query did not take place, there was no update here, either. For example, a typo corrected in the database was not updated in a performance indicator as it was not screened against the database. From a performance perspective, this was optimal, as well.
The repeat loop is principally a quick function which only becomes noticeably slower after a few thousand processes. The current arcplan realization at allocation (as mandatory with the numerator [OBJx] := [OBJx] +1), however, results in the increase of the running time upon allocation of values in relation to the aggregate amount of the objects of the opened documents. (This is a problem of the fundamental programming of arcplan Enterprise when identifying the object in the object stack which contains all objects of all open documents). In case of complex applications, the running time of the repeat loop is therefore much higher so that it may be running for seconds, rather than milliseconds, even in case of only few entries. Therefore, if possible, all functionalities should be implemented without repeat loop in order to ensure a good performance.
Subsequently, we provide an example which is frequently realized with the repeat loop even though there is an implementation option with other formulas.
The new functions READMETADATA() and PLACEMETADATA() offer a range of quite new possibilities to the arcplan designer. As shown in the arcCorporation Demo, data queries can be dynamically set up and modified via drag & drop.
The set-up of such a query is described below.
