![]() |
VOOZH | about |
MicroStrategy is an analytics and mobility platform that enables data-driven innovation. When you pair MicroStrategy with the CData ODBC Driver for Active Directory, you gain database-like access to live Active Directory data from MicroStrategy, expanding your reporting and analytics capabilities. In this article, we walk through adding Active Directory as external data in MicroStrategy Web and creating a simple visualization of Active Directory data.
The CData ODBC driver offers unmatched performance for interacting with live Active Directory data in MicroStrategy due to optimized data processing built into the driver. When you issue complex SQL queries from MicroStrategy to Active Directory, the driver pushes supported SQL operations, like filters and aggregations, directly to Active Directory and utilizes the embedded SQL engine to process unsupported operations (often SQL functions and JOIN operations) client-side. With built-in dynamic metadata querying, you can visualize and analyze Active Directory data using native MicroStrategy data types.
Information for connecting to Active Directory follows, along with different instructions for configuring a DSN in Windows and Linux environments (the ODBC Driver for Active Directory must be installed on the machine hosting the connected MicroStrategy Intelligence Server).
To establish a connection, set the following properties:
BaseDN: This will limit the scope of LDAP searches to the height of the distinguished name provided.
Note: Specifying a narrow BaseDN may greatly increase performance; for example, cn=users,dc=domain will only return results contained within cn=users and its children.
When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.
If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.
If you are installing the CData ODBC Driver for Active Directory in a Linux environment, the driver installation predefines a system DSN. You can modify the DSN by editing the system data sources file (/etc/odbc.ini) and defining the required connection properties.
[CData ActiveDirectory Sys] Driver = CData ODBC Driver for Active Directory Description = My Description User = cn = Bob F,ou = Employees,dc = Domain Password = bob123 Server = 10.0.1.2 Port = 389
For specific information on using these configuration files, please refer to the help documentation (installed and found online).
Once you have created a database instance in MicroStrategy Developer and connected it to a project, you can perform a data import of Active Directory data from MicroStrategy Web. Alternatively, you can create a new data source based on the ODBC Driver.*
SELECT CatalogName NAME_SPACE, TableName TAB_NAME FROM SYS_TABLES
SELECT DISTINCT CatalogName NAME_SPACE, TableName TAB_NAME, ColumnName COL_NAME, DataTypeName DATA_TYPE, Length DATA_LEN, NumericPrecision DATA_PREC, NumericScale DATA_SCALE FROM SYS_TABLECOLUMNS WHERE TableName IN (#TABLE_LIST#) ORDER BY 1,2,3
Using the CData ODBC Driver for Active Directory in MicroStrategy Web, you can easily create robust visualizations and reports on Active Directory data. Read our other articles on connecting to Active Directory in MicroStrategy and connecting to Active Directory in MicroStrategy Desktop for more examples.
Note: connecting using a ODBC driver requires a 3- or 4-tier architecture.
Download a free trial of the Active Directory ODBC Driver to get started:
Download NowLearn more:
๐ Active Directory IconThe Active Directory ODBC Driver is a powerful tool that allows you to connect with live Active Directory, directly from any applications that support ODBC connectivity.
Access Active Directory objects like you would a database - access Users, Groups, Roles, and Contacts, or define custom tables for any ObjectClass, and then perform SQL queries through a standard ODBC Driver interface.