Sample Subjects from the Archives. The Archives of the Teradata. Forum contains over 3.

To help navigate the Archives, there are additional indexes: For a list of the most recent threads, see: Recent Threads. Can T Install Ubuntu Desktop To Server. Yearly Indexes containing the threads posted during a given year. Index. By- Date Indexes containing the threads posted during a given month and year.

January 2. 00. 9 Index. The best way to find threads on a specific subject is to use the search box.

MS Excel: How to use the CONCAT Function (WS) This Excel tutorial explains how to use the Excel CONCAT function with syntax and examples. The Concatenate function in SQL combines multiple character strings together. The strings can come from the query or be a literal string.

Power BI and Direct. Query . You can either import data to Power BI, which is the most common way to get data, or you can connect directly to data in its original source repository, which is known as Direct. Query. This article describes Direct.

MS Access: DMax Function. This MSAccess tutorial explains how to use the Access DMax function with syntax and examples. Description. The Microsoft Access DMax. Code to count the number of records in a table/query in Microsoft Access, with the option to count the number of distinct values. A replacement for DCount().

Query and its capabilities, including the following topics: Different connectivity options for Direct. Query Guidance for when you should consider using Direct. Query rather than import Drawbacks of using Direct. Query Best practice for using Direct.

Query. In short, the best practice for using import versus Direct. Query is the following: You should import data to Power BI wherever possible. This takes advantage of the high performance query engine of Power BI, and provides a highly interactive and fully featured experience over your data. If your goals can't be met by importing data, then consider using Direct. Query. For example, if the data is changing frequently and reports must reflect the latest data, Direct. Query may be best.

However, using Direct. Query is generally only be feasible when the underlying data source can provide interactive queries (less than 5 seconds) for the typical aggregate query, and is able to handle the query load that will be generated. Additionally, the list of limitations that accompany use of Direct. Query should be considered carefully, to ensure your goals can still be met. The set of capabilities offered by Power BI for both connectivity modes – import and Direct.

Query - will evolve over time. This will include providing more flexibility when using imported data, such that import can be used in more cases, as well as eliminating some of the drawbacks of using Direct.

Query. Regardless of improvements, when using Direct. Query the performance of the underlying data source will always remain a major consideration. If that underlying data source is slow, then using Direct. Query for that source it will remain unfeasible. This topic covers Direct. Query with Power BI, and not SQL Server Analysis Services. Direct. Query is also a feature of SQL Server Analysis Services, and many of the details described below apply to its use, there are also important differences.

For information about using Direct. Query with SQL Server Analysis Services, see the whitepaper that details Direct.

Query in SQL Server Analysis Services 2. This article focuses on the recommended workflow for Direct. Query, where the report is created in Power BI Desktop, but also covers connecting directly in the Power BI service.

Power BI connectivity modes. Power BI connects to a very large number of varied data sources, encompassing: Online services (Salesforce, Dynamics 3. Databases (SQL Server, Access, Amazon Redshift, others) Simple files (Excel, JSON, others) Other data sources (Spark, Web sites, Microsoft Exchange, others)For these sources, it's usually possible to import the data to Power BI. For some it is also possible to connect using Direct. Query. The exact set of sources that support Direct.

Query is described in the Data Sources supported by Direct. Query article. More sources will be Direct. Query enabled in the future, focusing primarily on sources that can be expected to deliver good interactive query performance. SQL Server Analysis Services is a special case. When connecting to SQL Server Analysis Services, you can choose to import the data, or use a live connection.

Using a live connection is similar to Direct. Query, in that no data is imported, and the underlying data source is always queried to refresh a visual, but a live connection is different in many other regards, so a different term (live versus Direct. Query) is used. These three options for connecting to data – import, Direct. Query, and live connection – are explained in detail in the following sections. Import connections. When using Get Data in Power BI Desktop to connect to a data source like SQL Server, and you choose Import, the behavior of that connection is as follows: During the initial Get Data experience, the set of tables selected each define a query that will return a set of data (those queries can be edited prior to loading the data, for example to apply filters, or aggregate the data, or join different tables). Upon load, all of the data defined by those queries will be imported into the Power BI cache.

Upon building a visual within Power BI Desktop, the imported data will be queried. The Power BI store ensures the query will be very fast, hence all changes to the visual will be reflected immediately. Any changes to the underlying data will not be reflected in any visuals. It is necessary to Refresh, whereupon the data will be re- imported. Upon publishing the report (the .

Power BI service, a dataset is created and uploaded to the Power BI service. The imported data is included with that dataset. It is then possible to set up scheduled refresh of that data, for example, to re- import the data every day. Depending upon the location of the original data source, it might be necessary to configure an On- premises data gateway. When opening an existing report in the Power BI service, or authoring a new report, the imported data is queried again, ensuring interactivity. Visuals, or entire report pages, can be pinned as dashboard tiles. The tiles will be automatically refreshed whenever the underlying dataset is refreshed.

Direct. Query connections. When using Get Data in Power BI Desktop to connect to a data source, and you choose Direct. Query, the behavior of that connection is as follows: During the initial Get Data experience, the source is selected. For relational sources, this means a set of tables are selected and each still define a query that logically returns a set of data. For multidimensional sources like SAP BW, only the source is selected. However, upon load, no data will actually be imported into the Power BI store. Instead, upon building a visual within Power BI Desktop, queries will be sent to the underlying data source to retrieve the necessary data.

The time then taken to refresh the visual will depend on the performance of the underlying data source. Any changes to the underlying data will not be immediately reflected in any existing visuals. It is still necessary to Refresh, whereupon the necessary queries will be resent for each visual, and the visual updated as necessary. Upon publishing the report to the Power BI service, it will again result in a Dataset in the Power BI service, just as for import. However, no data is included with that dataset. When opening an existing report in the Power BI service, or authoring a new one, the underlying data source is again queried to retrieve the necessary data. Depending upon the location of the original data source, it might be necessary to configure an On- premises data gateway, just as is needed for Import mode if the data is refreshed.

Visuals, or entire report pages, can be pinned as Dashboard tiles. To ensure that opening a dashboard will be fast, the tiles are automatically refreshed on a schedule (for example, every hour). The frequency of this refresh can be controlled, to reflect how frequently the data is changing, and how important it is to see the very latest data.

Thus, when opening a dashboard, the tiles will reflect the data as of the time of the last refresh, and not necessarily the very latest changes made to the underlying source. An open dashboard can always be Refreshed to ensure it is up- to- date.

Live connections. When connecting to SQL Server Analysis Services (SSAS), there is an option to either import data from, or connect live to, the selected data model. If you select import, then you define a query against that external SSAS source, and the data is imported as normal.

If you select to connect live then there is no query defined, and the entire external model is shown in the field list. If you select Direct. Query, as visuals are built, queries are sent to the external SSAS source. However, unlike Direct.