Configure a report for use with Bulk Export in MicroStrategy

The Bulk Export feature enables a large report to be saved as a delimited text file. Using this feature, it is possible to retrieve result sets from a large dataset without having to load the entire dataset into memory.

PS: Once a report is setup for bulk export it cannot be used as a regular report. So if the report needs to be run as a normal report and as a bulk export report, the first step is to make a copy of the report for use with bulk export.

Configure Bulk Export

Bulk Export options are only available in MicroStrategy Developer. Open a 3-tier connection using MicroStrategy Developer and edit the desired report.
Go to 'Data' on the top menu bar.
Select 'Configure Bulk Export':
Specify any additional desired configuration options.

General Settings

Bulk export database instance: This is the database instance to use to store the bulk export results. Temporary tables will be created in this database to hold the intermediate export results.

Default delimiter: How the data in the resulting text file will be delimited. Available options include: Comma, Tab, Semicolon, Colon, Space, and Other to specify another character

Advanced Settings:

Governing > Maximum time for SQL execution to build table (sec): Maximum amount of time that the SQL used to build the table may run before being terminated.

Governing > Maximum time for exporting data to file (sec): Maximum time allowed to write the completed results to file. If this fails, a timeout error will occur.

Governing > Numbers to rows retrieved in each step: Maximum number of rows to retrieve from the temp table and write to the file at a time.

Table creation properties > Table Space: The database table space in which the temporary table for the export is created.

Table creation properties > Table Prefix: Prefix to use when creating, inserting, and selecting data from the table.

SQL Statements:

Bulk export data governing > SQL to be executed prior to exporting data to file (after populating the table): SQL statements to be executed after the table is populated with all of the data, but before the data is exported to a file.

After saving and closing the report, the icon will change in MicroStrategy Developer and the report type will be 'Non Interactive':

Setup the Bulk Export Subscription

Only file based subscriptions can be used with bulk export, thus bulk exports can only be subscribed to in MicroStrategy Web.

Using MicroStrategy Web, navigate to the bulk export report, and setup a file based subscription. The options available are the same as any other file subscription that can be created:

When the subscription runs it will incrementally write data to the file based on the governing setting. The resulting file will be a text file:

Comments

MicroStrategy URL API Parameters

MicroStrategy URL Structure The following table summarizes the root URL structure used for every request to MicroStrategy Web. Environment Main Application URL Administration URL J2EE http://webserver/MicroStrategy/servlet/mstrWeb http://webserver/MicroStrategy/servlet/mstrWebAdmin .NET http://webserver/MicroStrategy/asp/Main.aspx http://webserver/MicroStrategy/asp/Admin.aspx Every request sent to MicroStrategy Web calls a central controller. Parameters are appended to Main.aspx or mstrWeb (in a .NET and J2EE environment, respectively) to indicate to the controller how the request should be internally forwarded and handled. The following examples show a URL for accessing a MicroStrategy folder when the user does not have an existing session. The URL contains not only the parameters needed to connect to MicroStrategy Web, but also the parameters needed to log on and create a session. J2EE environment: <a href="http:...

Microstrategy Report Execution Process

The Report Execution Process Report execution process at a high level: The report execution process is a three-step process: 1. Query Stage : Retrieve data from the warehouse 2. Populate and Evaluate : Fill report data required for display 3. Cross-tab : Pivot and display sorting and page-by Each of the engines plays an important part in the report execution process. As you can imagine, the SQL Engine performs its role during the Query stage while the Query Engine and Analytical Engine can be involved in all three stages.

Case functions Microstrategy

Ca se functions Microstrategy Case functions return specified data in a SQL query based on the evaluation of user-defined conditions. In general, a user specifies a list of conditions and corresponding return values. Case This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. If all conditions are false, a default value is returned. Case can be used for categorizing data based on multiple conditions. This is a single-value function. Syntax Case ( Condition1 , ReturnValue1 , Condition2 , ReturnValue2 ,..., DefaultValue ) Example Case(([Total Revenue] < 300000), 0, ([Total Revenue] < 600000), 1, 2) sum(Case (Day@DESC in (“Sat”,”Sun”), Sales, 0) {~+} Sum(Case(Category@DESC In("Books","Electronics"),Revenue,0)){~+} CaseV (case vector) CaseV evaluates a single metric and returns different values according to the results. It can be used to perfo...

Email Subscription in Microstrategy

Create Email Subscription in Microstrategy Creates an email subscription. Do not include any leading or trailing spaces in the ANSWER parameters. This causes a SQL error and prevents the command from executing. Ex: CREATE EMAILSUBSCRIPTION "New Multi Users" FOR OWNER "administrator" SCHEDULE "Books Closed" CONTACTGROUP "TEST" CONTENT "Electronics Revenue by Region" IN FOLDER "\Public Objects\REPORTS\SUBJECT Areas\Sales and Profitability Analysis" IN PROJECT "MicroStrategy Tutorial" DELIVERYFORMAT HTML EXPIRATIONDATE NEVER EXPRIED FILENAME "file_name" SUBJECT "Test REPORT" MESSAGE "Please Test"; CREATE EMAILSUBSCRIPTION [ subscription_name ] [FOR OWNER login_name ] SCHEDULE schedule_name (ADDRESS address_name | USER user_name | CONTACT contact_name [ADDRESS contact_ address_name ] | CONTACTGROUP contact_group_name ) CONTENT ( report_or_document_name IN FOLDER loc...

Personalizing file locations, email and file subscriptions using macros in Microstrategy

Personalizing file locations MSTr allows to dynamically specify the File Location and Backup File Location in a file device using macros. For example, if you specify the File Location as C:\Reports\{&RecipientName}\ , all subscriptions using that file device are delivered to subfolders of C:\Reports\ . Subscribed reports or documents for each recipient are delivered to a subfolder with that recipient’s name, such as C:\Reports\Jane Smith\ or C:\Reports\Hiro Protagonist\ . The table below lists the macros that can be used in the File Location and Backup File Location fields in a file device: Description Macro Date on which the subscription is sent {&Date} Time at which the subscription is sent {&Time} Name of the recipient {&RecipientName} User ID (32-character GUID) of the recipient {&RecipientID} Distribution Services add...

Client Rendering Optimizations for Dashboard Performance Optimizations

The amount of data retrieved and objects being used in a Report Services Dashboard have a direct impact in the size of the final Dashboard. The bigger the Dashboard size the longer it will take to be prepared, be sent to the client, and render. Client Rendering Once the data reaches the end user's browser window the data has to be formatted according to the definition of the Dashboard as specified in the formatting set by the architect. To do so the browser will have to either build the HTML page in DHTML mode or initialize the flash container and parse the XML. Client rendering greatly varies depending on the hardware used. More powerful machines will render dashboard faster for a list of recommended client hardware specifications please refer to the Readme File for the specific version of MicroStrategy. Optimization Techniques common to DHTML and Flash Client rendering time greatly relies in the amount of XML that needs to be parsed. In order to ensure that...

Microstrategy "Error type: Odbc error. Odbc operation attempted

"Error type: Odbc error. Odbc operation attempted: SQLExecDirect. [HYT00:0: on SQLHANDLE] [MicroStrategy][ODBC Oracle Wire Protocol driver]Timeout expired" is shown when executing reports from Web When users are trying to execute some reports in MicroStrategy web in particular, they may receive the Error “SQL Generation Complete Index out of range” and “Timeout expired” error as shown below: Possible Causes: One possible cause is that the MicroStrategy Intelligence Server using a cached database connection that was already dropped by the RDBMS. To resolve this: Admin should delete the database connection caches and create a new DSNs in case they are sharing DSNs to connect to different databases. In addition, change the settings for the ‘Connection lifetime’ and the ‘Connection idle time out’. Follow the steps below to perform the mentioned changes and verify the report after each step and some of the settings require i-server r...

Microstrategy Caches explained

Microstrategy Caches Improving Response Time: Caching A cache is a result set that is stored on a system to improve response time in future requests. With caching, users can retrieve results from Intelligence Server rather than re-executing queries against a database. To delete all object caches for a project 1 In Developer, log into a project. You must log in with a user account that has administrative privileges. 2 From the Administration menu, point to Projects , and then select Project Configuration . The Project Configuration Editor opens. 3 Expand Caching , expand Auxiliary Caches , then select Objects . To delete all configuration object caches for a server 1 Log in to the project source. 2 From the Administration menu in Developer, point to Server , and then select Purge Server Object Caches . 4 Click Purge Now . To purge web cache follow the steps in the link ...

Microstrategy Report Services documents and dashboards

Microstrategy Report Services documents vs Dashboards A MicroStrategy Report Services document displays data coming from multiple reports, with the data laid out and designed in presentation-quality format. Most data on a document is from one or more underlying datasets. A dataset is a standard MicroStrategy report. Other document components that do not originate from the dataset, such as static text used for a title or heading, page numbers, and images, are added by the document's designer and are stored in the document's definition. A Report Services (RS) dashboard is a special type of document. An RS dashboard is commonly only one page long, is intended to be viewed online, and usually provides interactive features that let analysts change how they view the dashboard’s data, as well as what data they are viewing. A broad selection of widgets and a wide variety of formatting options allow you to design a customized, interactive dashboard. Both documents and RS dashb...

Microstrategy Analytics

Search This Blog