Overview
The Lyftron Provider for SQL Analysis Services offers the most natural way to access SQL Analysis Services data from Lyftron with ease and also enables to connect with BI, MDM & ML tools, Data warehouses, Databases and other SAAS based applications with zero code and zero infrastructure requirements. The provider wraps the complexity of accessing SQL Analysis Services data into easy-to-integrate relational fully managed ANSI Sql format. Make faster and better business decisions with Lyftron’s SQL Analysis Services data provider and automatically build your data migration pipelines in minutes, not months
The provider hides the complexity of accessing data and provides additional powerful security features, smart caching, batching, socket management, and more.
Key Features
- Comprehensive Delta load mechanism.
- Real-time access to SQL Analysis Services.
- Comprehensive full support of ANSI Sql to query data with ease.
- Collaborative query processing.
Prerequisites
The user must have credentials for SQL Analysis Services, Lyftron and your destination data warehouse, lake or database to perform the data pipeline operation with Lyftron
Establishing a Connection with Lyftron's Quickstart Steps
Create your SQL Analysis Services connection with Lyftron by following the 5 easy steps show below:
Step1. Add your connection
Click on Connect section on the left panel → Click on Add Connection button
Step2. Select your connector
In the connector selection panel, search and click SQL Analysis Services for your connection
Step3. Enter your connection details
In the Connection String section enter the values of the below parameters. The following connection string is required to establish SQL Analysis Services connection with Lyftron.
"User=myuseraccount;Password=mypassword;URL=http://localhost/OLAP/msmdpump.dll;"| Key | Value | Field |
| Connection Name | Enter your connection details | Required |
| User | your SQL Analysis Services useraccount | Required |
| Password | your SQL Analysis Services password | Required |
| URL | http://localhost/OLAP/msmdpump.dll | Required |
| Logfile** | Use the logfile option to debug your job and provide your connection name to generate the log file. [ConnectionConfigurationPath]\Connection_name_log.tx | Optional |
| Verbosity** | Choose verbosity 1-5 based on the severity of debugging | Optional |
** For more information, check the Lyftron logging and debugging section.
If you want more detailed information about how to establish a connection with Lyftron, click on Lyftron Connection Quick Start guide.
Step4. Test your connection
Once you are done entering your connection details, simply click on the Test Connection button to test the connectivity. In case your connection fails, add Logfile and Verbosity parameters and check the Lyftron logging and debugging section, to debug the error.
Step5. Save your connection
Hurray! Now you have successfully connected with the Lyftron SQL Analysis Services connector and can utilize the connector to Extract, Warehouse, Analyze, Visualize and Share your data.
Data Model
System Tables
The following table lists and describes each system base table in SQL Server.
| BaseTable | Type | Description |
| sys.sysnsobjs | Tables | Exists in every database. Contains a row for each namespace-scoped entity. This table is used for storing XML collection entities. |
| sys.syscolpars | Tables | Exists in every database. Contains a row for every column in a table, view, or table-valued function. It also contains rows for every parameter of a procedure or function. |
| sys.systypedsubobjs | Tables | Exists in every database. Contains a row for each typed subentity. Only parameters for partition function fall into this category. |
| sys.sysiscols | Tables | Exists in every database. Contains a row for each persisted index and statistics column. |
| sys.sysscalartypes | Tables | Exists in every database. Contains a row for each user-defined or system type. |
| sys.sysdbreg | Tables | Exists in the master database only. Contains a row for each registered database. |
| sys.sysxsrvs | Tables | Exists in the master database only. Contains a row for each local, linked, or remote server. |
| sys.sysrmtlgns | Tables | This system base table exists in the master database only. Contains a row for each remote login mapping. This is used to map incoming logins that claim to be coming from a corresponding server to an actual local login. |
| sys.syslnklgns | Tables | Exists in the master database only. Contains a row for each linked login mapping. Linked login mappings are used by remote procedure calls and distributed queries that emanate from a local server out to a corresponding linked server. |
| sys.sysxlgns | Tables | Exists in the master database only. Contains a row for each server principal. |
| sys.sysdbfiles | Tables | Exists in every database. If the column dbid is zero, the row represents a file that belongs to this database. In the master database, the column dbid can be nonzero. When this is the case, the row represents a master file. |
| sys.sysusermsg | Tables | Exists in the master database only. Each row represents a user-defined error message. |
| sys.sysowners | Tables | Exists in every database. Each row represents a database principal. |
| sys.sysobjkeycrypts | Tables | Exists in every database. Contains a row for each symmetric key, encryption, or cryptographic property associated with an object. |
| sys.syscerts | Tables | Exists in every database. Contains a row for each certificate in a database. |
| sys.sysasymkeys | Tables | Exists in every database. Each row represents an asymmetric key. |
| sys.ftinds | Tables | Exists in every database. Contains a row for each full-text index in the database. |
| sys.sysxprops | Tables | Exists in every database. Contains a row for each extended property. |
| sys.sysallocunits | Tables | Exists in every database. Contains a row for each storage allocation unit. |
| sys.sysrowsets | Tables | Exists in every database. Contains a row for each partition rowset for an index or a heap. |
| sys.sysrowsetrefs | Tables | Exists in every database. Contains a row for each index to rowset reference. |
| sys.syslogshippers | Tables | Exists in the master database only. Contains a row for each database mirroring witness. |
| sys.sysremsvcbinds | Tables | Exists in every database. Contains a row for each remote service binding. |
| sys.sysconvgroup | Tables | Exists in every database. Contains a row for each service instance in Service Broker. |
| sys.sysxmitqueue | Tables | Exists in every database. Contains a row for each Service Broker transmission queue. |
| sys.sysdesend | Tables | Exists in every database. Contains a row for each sending endpoint of a Service Broker conversation. |
| sys.sysdercv | Tables | Exists in every database. Contains a row for each receiving endpoint of a Service Broker conversation. |
| sys.sysendpts | Tables | Exists in the master database only. Contains a row for each endpoint created in the server. |
| sys.syswebmethods | Tables | Exists in the master database only. Contains a row for each SOAP-method defined on a SOAP-enabled HTTP endpoint that is created in the server. |
| sys.sysqnames | Tables | Exists in every database. Contains a row for each namespace or qualified name to a 4-byte ID token. |
| sys.sysxmlcomponent | Tables | Exists in every database. Each row represents an XML schema component. |
| sys.sysxmlfacet | Tables | Exists in every database. Contains a row for each XML facet (restriction) of XML type definition. |
| sys.sysxmlplacement | Tables | Exists in every database. Contains a row for each XML placement for XML components. |
| sys.syssingleobjrefs | Tables | Exists in every database. Contains a row for each general N-to-1 reference. |
| sys.sysmultiobjrefs | Tables | Exists in every database. Contains a row for each general N-to-N reference. |
| sys.sysobjvalues | Tables | Exists in every database. Contains a row for each general value property of an entity. |
| sys.sysguidrefs | Tables | Exists in every database. Contains a row for each GUID classified ID reference. |
| sys.sysclsobjs | Tables | Exists in every database. Contains a row for each classified entity that shares the same common properties that include the following:Assembly,Backup device,Full-text catalog,Partition function,Partition scheme,File group,Obfuscation key |
| sys.sysbinobjs | Tables | Exists in every database. Contains a row for each Service Broker entity in the database. Service Broker entities include the following: Message type,Service contract,Service |
Advanced Settings
To view a detailed advanced settings options, go to SQL Analysis Services Advanced Settings. Complete list of the parameters you can configure in the connection string can be found by clicking Connection String Parameters.