Power BI Teradata integration for large warehouses
Power BI Teradata integration puts a modern report layer on a warehouse that often holds decades of enterprise data. Microsoft documents a Teradata database connector with Import and DirectQuery support. It needs a data provider from Teradata on the machine, and online refresh runs through a gateway. With those pieces planned, analysts get fast reports without moving the warehouse.
- Teradata database connector
- Import and DirectQuery
- Gateway for the service
Last updated
How does Power BI Teradata integration work?
The author selects the Teradata database connector and types the server name. Then Power BI Desktop asks whether to import the data or use DirectQuery. After sign-in, the navigator shows the databases and tables the account may read.
A prerequisite sits underneath. Microsoft's article says the .NET Data Provider for Teradata must be on the computer before a connection will work. So we install it on each author's machine and on the gateway server as well.
For sign-in, the article lists database and Windows authentication. We usually ask for a dedicated reporting account with read access to the agreed views, because a personal login fails the day its owner changes role.
Three design choices for a Teradata source
A large warehouse rewards a little planning before anyone clicks Load.
Import summaries
Load data at the grain the report needs. Then visuals stay quick and the warehouse rests between refreshes.
DirectQuery for detail
Leave very large tables in Teradata and query them on demand. However, every click then depends on warehouse speed.
Aggregations on top
Combine both, so common questions hit an imported summary while rare ones reach the detail.
Why do views matter when Teradata feeds a report?
Warehouse tables carry technical columns, history rows and codes. Report authors should not have to decode them. So we ask for reporting views that expose clean, current and well-named columns.
Views also help performance. When a view filters and joins in the database, Power Query can often fold the rest of its steps into one SQL statement. As a result, less data travels and refresh finishes sooner.
Workload rules deserve a word too. Many Teradata sites use workload management to protect priority jobs. Therefore we agree a class and a time window for reporting queries with your database administrators first. That plan also tells us when a refresh can run, so nobody finds out by accident during a month-end load. Wider warehouse design is covered under Power BI data warehouse consulting.
Pitfalls in a Power BI Teradata integration
These are the most common issues on Teradata projects.
- The data provider is missing on the gateway server
- Whole fact tables imported when a summary would do
- DirectQuery pages with too many visuals
- Refresh jobs that collide with nightly loads
- A personal account used for scheduled refresh
- Custom SQL that stops later steps from folding
Our process for Power BI Teradata integration
Four stages take the work from a first call to a documented handover.
Understand the warehouse
First we meet the people who run Teradata and learn the subject areas, views and rules.
Fix scope in writing
Then a written quote names the models and reports, so both sides know what done means.
Connect through the gateway
Next we install the provider, set up the gateway and test sign-in from the service.
Tune and document
Finally we tune slow queries with your administrators and leave notes on every source object.
Teradata data in Power BI: questions teams ask
Does Power BI have a native Teradata connector?
Yes. Microsoft's Power Query connector list includes a Teradata database connector, and the article marks it as generally available. It lists Import and DirectQuery as supported for Power BI semantic models. The article also names the .NET Data Provider for Teradata as a prerequisite on the computer.
Does a Power BI Teradata connection need a gateway?
In the online experience, yes. Microsoft's article says you must select an on-premises data gateway for this connector, whether the Teradata database is on your local network or online. So we set up a gateway machine, install the Teradata provider on it and keep it near the warehouse.
Should we use Import or DirectQuery with Teradata in Power BI?
It depends on size and freshness. Import gives the fastest reports and works well up to the limits of your capacity. DirectQuery keeps data in the warehouse and suits very large or fast-changing tables. A blend of the two is common. We test with real volumes before we recommend one.
Can we move off Teradata later without rebuilding reports?
Often, yes, if the model stands between the source and the reports. When the warehouse moves to another platform, we repoint the queries and keep the measures and pages. Some rework is normal, since SQL dialects differ. A clean semantic model keeps that effort small.
How do we begin a warehouse reporting project?
Reach us on (480) 485-7373 or by message. We reply within 2 hours and offer a free 30-minute assessment with one of our consultants. Power BI Agency is a division of Sataware Technologies and is independent of Microsoft. All delivery is online.
Let's build your first dashboard together.
Tell us what you report on today. A consultant replies within 2 hours with next steps.
Trusted partners
Microsoft Solutions Partner · AWS Partner
Cloud & AI Platforms
Azure SQL, Microsoft Fabric and the data pipelines behind your reports.
AI Business Solutions
Power BI reporting on your Dynamics 365, Business Central and Power Platform data.
Security
Row-level security and Entra ID sign-in on every report and workspace.
Amazon Web Services
Power BI on your AWS data, with connectors for Redshift, Athena and S3.