{"id":3364,"date":"2018-03-22T11:20:17","date_gmt":"2018-03-22T11:20:17","guid":{"rendered":"https:\/\/www.threesl.com\/blog\/?p=3364"},"modified":"2025-02-17T08:21:00","modified_gmt":"2025-02-17T08:21:00","slug":"housekeeping","status":"publish","type":"post","link":"https:\/\/www.threesl.com\/blog\/housekeeping\/","title":{"rendered":"Housekeeping"},"content":{"rendered":"

Keeping Cradle in Tip Top Condition<\/h2>\n

This article will highlight a set of housekeeping tips to keep Cradle running smoothly and provide a good user environment.<\/p>\n

Alerts<\/h3>\n

Whilst alerts are a very useful feature telling users\u00a0 that an aspect or item of their project has changed, users sometimes forget to clear their alerts from their accounts. You could ask each user to select old read\/unread alerts and delete them. However, an administrative user with both PROJECT<\/em> <\/b>and ACCESS_BYPASS <\/em>privileges can tidy alerts for ALL<\/em> users<\/p>\n

\"how
Housekeeping Alerts<\/figcaption><\/figure>\n

Selecting the Project<\/strong> tab, then Delete Alerts<\/strong><\/a> will show a dialog that lets the administrator choose a range of ALL users’ alerts to delete. This will remove read and unread alerts from the database.<\/p>\n

\"Automatic
Project Setup – Alert Management<\/figcaption><\/figure>\n

Additionally Alerts <\/em>can be tidied up by each user automatically each time they log out. This setting can be found in the Project Setup<\/em> under Alerts<\/em>.<\/p>\n

Definitions<\/h2>\n

These can include Queries, Views, Forms, Matrices, Metrics, Reports, Graphs, Dashboards, Navigations, Start Pages, Graphics Print Settings, Hierarchy Diagram Properties, Capture Setups, Report Styles, Graph Styles, Export \/ Import Formats.
\n<\/em><\/p>\n

They are stored in different groupings, Personal, Project, User, Team, User Type, System and Automatic<\/em>. These groups allow the definitions to be shared according to their intended use. Project<\/em> for example is available to everyone working on that project, whereas User Type<\/em> definitions match someone’s role on that project and are available to users holding that role. Personal definitions however, will be available to that person, across projects.<\/p>\n

Sometimes duplicates or old definitions can accumulate and need tidying up. The definitions manager<\/em> <\/a>allows users to manipulate.<\/p>\n

From the Project<\/em> toolbar selecting the Definitions Manager<\/strong> will show the following dialog.<\/p>\n

\"showing
Definitions Manager<\/figcaption><\/figure>\n

Using the side buttons, definitions can be moved, copied<\/em> and deleted. <\/em>This would allow, say a team leader with creation privileges, to develop a number of queries or views and then move them into User Types <\/em>for use by users who are not allowed to modify or create the definitions, themselves.<\/p>\n

Depending on the location of the definition users may need one or more privileges from CREATE_DEFS, PROJECT, TEAM_LEADER or indeed ACCESS_BYPASS.<\/p>\n

DPack<\/h2>\n

The DISAM database file system used by Cradle consists of file pairs of data and index files. After time, it is possible, that a number of blank areas will appear in the data file, as a result of large numbers of records having been deleted. Whilst this is perfectly normal operation, it can mean the data file is larger than it needs to be.<\/p>\n

\"running
dpack Utility<\/figcaption><\/figure>\n

The DPack utility<\/a> can be used to re-write these files more compactly and rebuild the indexes. This is not considered an everyday operation and would normally only be performed by and IT administrator. This should only be performed when the CDS (Cradle Database Server) is not running.<\/p>\n

    \n
  1. Make sure you have a backup of the entire project directory – incase a power-cut or machine failure occurs during crucial operations<\/li>\n
  2. Move to the directory to be compacted<\/li>\n
  3. Run the following command (c_dpack on Linux, dpack.exe on Windows\u00ae)
    \n\"%CRADLEHOME%\\bin\\exe\\windows\\dpack.exe\" tlb1alrt<\/code> Where tlb1 <\/em>is the project code<\/em> and alrt<\/em> is the particular database file to re-pack.<\/li>\n
  4. To complete this for all files in the directory running a batch-file or script
    \ne.g. on Windows\u00ae
    \n@echo OFF
    \nfor \/F %%f in ('dir \/B \"C:\\Data\\cradle_projects\\TLB1\\*.dat\"') do (
    \n\u00a0\u00a0\u00a0<\/b>echo Processing file %%~nf
    \n\u00a0\u00a0\u00a0<\/b>\"%CRADLEHOME%\\bin\\exe\\windows\\dpack.exe\" %%~nf
    \n)<\/code>
    \nWhere C:\\Data\\cradle_projects\\TLB1\\TLB1<\/samp> is the directory for the project.<\/li>\n<\/ol>\n

    Cradle History<\/h2>\n

    Keeping track of what you’ve been doing is really useful, the history sidebar shows the queries you have run and the items you have opened.<\/p>\n

    However, sometimes you may have a long list of entries from a particular day, you may then want to work on a different part of the project. In this instance it is sometimes useful to clear your history and start afresh. In the History Sidebar <\/em>you can choose what to clear by selecting and right clicking items in the menu.<\/p>\n

    \"Options
    Clearing History<\/figcaption><\/figure>\n

    Larger amounts can be cleared through the Clear Browsing History<\/strong> option on the Project tab.<\/em><\/a><\/p>\n