Glossary
Bragi's glossary defines key terms used in the documentation.
- App Instance
Each App Instance represents a running or registered Bragi application such as a WebApp or Scheduler across different servers or environments. Tracking these instances helps with deployment, load balancing, and troubleshooting.
- Bra
This is the 3 letter extension of the Bragi files. For example '2024-01-01-BragiExport.bra'
- Bragi Metadata
The Microsoft SQL Server Database where Bragi stores metadata related to its own operations and your warehouse setup.
- Config
Config is used as general catch all for the main Bragi components, including Archives, Code, Jobs, Stages, Views and Stored Procedures.
- Connection String
A Connection String is used to connect Bragi to a database. It is a string containing information about a data source and the necessary information to connect to it.
- Daily Summary
A report displayed on Bragi's dashboard summarising Scheduler Job activity over the last 24 hours. You can choose to receive this summary via email.
- Deployment
A Deployment is the process through which changes to configs are promoted between environments. For example:
Moving phase 1 of your warehouse from Develop to Test for users to evaluate.
Moving configs to Production once tested and approved by users.
- DLL
Dynamic-link Library (DLL) is Microsoft's implementation of a shared library. Commonly used on the Windows platform. Uses the file extension .dll
- Environment
An Environment in Bragi represents a distinct Warehouse database. In a typical set up there are three environments: Develop, Test, and Production, each with its own Warehouse SQL Database. You can only make changes in the first environment, these changes can then be deployed up to the next environment in a controlled manner. Switch between environments using the dropdown in the top-left of the Navigation Panel.
- Export
The act of exporting a package (.bra file) from your instance of Bragi. This could then be shared internally (for use in other instances of Bragi) or externally with another business.
- High Watermarks
High Watermarks help speed up data loads by tracking the last loaded value from one or more selected columns. Each time a load runs, Bragi remembers the highest value seen for those columns. On the next run, it only loads new rows that are greater than those stored values.
- Import
The act of importing a package (.bra file) into your instance of Bragi. This goes to the develop environment.
- Modal
A popup dialog that appears over the WebApp’s content.
- Navigation Panel
The sidebar on the WebApp featuring the Bragi logo and navigation links.
- Scheduler
Bragi Schedulers are responsible for running jobs on a timed schedule. There can be one per environment or one for all environments. Schedulers can run on the same server as the WebApp, but it is recommended to run each Scheduler on its own dedicated server.
- SQL View
A SQL view is a virtual table based on a SELECT query. It references existing database tables or other views and is a snapshot of the database.
- Stored Procedure
A Stored Procedure is a group of SQL statements that can be executed.
- Table
A table stores and organises data in a structured, two-dimensional format (similar to a spreadsheet). It consists of rows and columns.
- UNC Path
"Universal Naming Convention" (UNC) is a format for specificity the location of resources on a LAN. It takes the format \server-name\shared-resource-pathname.
- (Data) Warehouse
This is the SQL Database containing your tables, views, stored procedures and important business data generated though Bragi. A separate database exists for each environment you have configured.
- WebApp
The Bragi website used to manage and configure your Warehouse. It runs on IIS and should ideally be the only website hosted on that IIS instance.