Notebook FAQ

important specifications related to Codatum notebook

Notebook

Are notebooks created by a user still accessible after the user is deleted?

Private notebooks become inaccessible, but other notebooks remain accessible.

Are changes to parameters and charts independent for each user?

Changes to parameters, SQL, and charts are immediately reflected and displayed to all users viewing the same Page. These changes are saved as the state within the notebook.

However, settings related to the appearance of the Page, such as toggle states of SQL Blocks or List items, are not synchronized between users.

Is the cache used when executing Run all ?

Available caches are used when executing Run all.

For more details, please refer to the SQL Block Cache page.

If you do not wish to use the cache, for instance, after updating the data source, please execute all SQL Blocks from the top-right corner of the page by selecting Run all without cache.

Are there any limitations on Notebooks?

The maximum size per notebook is 10MB.

Having a large amount of content may impact performance, particularly loading times and conflict resolution. To maintain smooth performance, we recommend keeping notebooks concise. If a notebook becomes too large, consider creating a new notebook instead of adding more Pages.

Recommended ways to manage large Notebooks:

• Export a notebook and import pages into a new notebook If a notebook is growing too large, you can export the original notebook, create a new notebook, and import some pages there. When moving pages, ensure that referenced SQL Blocks are properly managed to avoid breaking dependencies.

• Archive old notebooks If you no longer need to edit a large notebook but still want to keep its content, you can duplicate it and set the duplicate as read-only for archival purposes. After that, you may delete unnecessary pages from the original notebook to reduce its size.

Doc Page

When the content of a Doc Page becomes lengthy, how do I know when to split it into multiple Pages?

As the content of a Doc Page becomes lengthy, the difficulty in understanding the analysis increases.

As SQL Blocks can reference SQL Blocks from other pages, you can continue the analysis by splitting the Doc Page at any time.

Similarly, parameters can also be created and referenced across different pages.

As the number of Pages increases, how do I know when to split the notebook?

When the number of pages increases, finding where specific analyses were done becomes difficult.

Additionally, as the number of elements within a page or the number of pages increases, the performance of the entire notebook may slow down.

If you want to share SQL statements across notebooks, you can store them using the Query and refer to them from multiple notebooks.

If the number of pages increases considerably, save only the reusable SQL statements as query and create a new notebook.

SQL Block

Column names of tables referenced within an SQL Block are not being suggested.

Column name suggestions, along with metadata and schema displays, are limited to Table Ref or executed SQL Block Ref.

Please note that suggestions and schema displays are not available when using table IDs as strings or when referring to Saved Queries