Jet from insightsoftware

Creating an Execution Package
Creating an Execution Package Overview Execution packages will automatically update the staging database, data warehouse, and OLAP cubes on a scheduled bases. This article details the following: Create Notifications (Optional) Create an Execution Package Exclude Objects from an Execution Package Fully Load Tables During a Scheduled Execution Specify an Execution S...
Merge Steps property explained
Merge Steps property explained Overview If multiple steps are added in an execution package, then these are treated as an ordered list. The steps will be executed in the order they appear in the list. When using multi-threaded execution, JDM 2014 will start steps in parallel without considering dependencies between objects. With the Merge option for execution packages, JDM 2014 will no long...
Default Execution Package
Default Execution Package Overview The Jet Data Manager's Managed Execution feature (v2014 SR1 and higher) allows the JDM to decide the execution order of the individual objects while respecting the implicit and explicit dependencies between objects.  However, when you do a manual execution of the project by clicking the Manual Deployment and Execution button or by running a full...
Execution Logging and Statistics
Execution Logging and Statistics Overview When a table, dimension, or cube is executed through an execution package, the Jet Data Manager will log information regarding the event.  You have the ability to view the settings used for the execution.  The settings are stored in an XML format and displayed as a read-only version of the execution package setup window. Viewing the Execution ...
Executing External SSIS Packages
Executing External SSIS Packages The Jet Data Manager supports execution of packages stored in Integration Services Catalogs (SQL 2012) and in the file system. Specifying a SSIS Package Location On the Execution tab, right-click External Executables and click Add Execute External SSIS Package Step In the drop-down for Location ...
Allow Data Source Failure During Execution
Allow Data Source Failure During Execution Overview There are oftentimes some source systems in a business intelligence solution that are less than critical for your reporting. It is possible to configure the Jet Data Manager so that the entire execution does not stop because the software cannot reach any of these non-critical systems. Instead, the organization can choose to keep the newest...
Defining Dependencies for the Scheduler Service
Defining Dependencies for the Scheduler Service OVERVIEW There are times when setting up the Jet Data Manager Scheduler service correctly will still not allow the service to start automatically upon server restart. In these cases, a dependency needs to be set on the Jet service for SQL Server. PROCESS In an elevated (administrator) command prompt on the machine that hosts the J...
Resuming a failed Execution
Resuming a failed Execution Overview It is possible to resume a failed execution from the point of failure. This is useful since, with managed execution, you cannot always determine in what order the JDM will execute tables. This means that if an execution fails, a complete restart of the execution was previously the only way to ensure that everything is executed correctly. This feature was...
Using Prioritizations in an Execution Package
Remote Control for Execution Packages
Remote Control for Execution Packages Overview There are cases where it is desirable for an organization to be able to run an execution package to update the data in the data warehouse and cubes without having to wait for the scheduled refresh. For example; at the end of the month, the finance team may post some additional transactions and want to refresh the data immediately, so that t...
Additional Service Setup
Additional Service Setup Overview The Jet Data Manager Server Scheduler service operates a single Jet Project Repository. If your organization has multiple project repositories an additional instance of the Jet Data Manager Server Scheduler service must be created and associated with the subsequent project repository. An example of when this might be necessary is when your organization ...
First Page
Back
For an optimal Community experience, Please view on Desktop