powerbi发布本地

Whether you’ve been using PowerBI for a while or you’re just getting started with it, chances are you’ll want to source at least some of your data from on-premises systems. Be that SQL server databases, Oracle, SSAS etc. The same process even applies if you’re sourcing from AWS which I’ll go into in more detail below. All of these data sources will require Microsoft’s On-Premises Data Gateway.

无论您是使用PowerBI已有一段时间还是刚刚开始使用PowerBI，都有可能需要从本地系统中获取至少一些数据。 是SQL Server数据库，Oracle，SSAS等。如果您从AWS采购，则同样的过程同样适用，我将在下面更详细地介绍。 所有这些数据源都将需要Microsoft的本地数据网关 。

Originally branded the PowerBI Enterprise Gateway (in line with the other option of the “Personal Gateway” you could set up locally when creating a report in PowerBI Desktop). The product was later expanded to encompass several Azure services as shown in the handy diagram below.

最初是PowerBI企业网关的商标（与“个人网关”的其他选项一致，您可以在PowerBI Desktop中创建报表时在本地设置）。 稍后将产品扩展为包含几个Azure服务，如下图所示。

The On-Premises Data Gateway is an application which is installed within your network to give encrypted & compressed connectivity between Azure cloud services and your on-premises data.

本地数据网关是一个安装在网络中的应用程序，用于在Azure云服务与本地数据之间提供加密和压缩的连接。

The application itself can be installed on an existing or separate server/VM. The main performance considerations here are network throughput and uptime. The importance of these factors depends on your environment though.

该应用程序本身可以安装在现有或单独的服务器/ VM上。 这里主要的性能考虑因素是网络吞吐量和正常运行时间。 这些因素的重要性取决于您的环境。

I.e. The data gateway can be installed on a Windows 7 machine or higher (and further system requirements can be found at the documentation link in the first paragraph) but as you’d expect, as soon as this machine is powered off you lose all connectivity to your on-premises data sources in PowerBI.

即，数据网关可以安装在Windows 7或更高版本的计算机上（进一步的系统要求可以在第一段的文档链接中找到），但是正如您所期望的那样，在关闭计算机电源后，您将失去所有连接到PowerBI中的本地数据源。

I’ll go into more detail on high availability further on though as there’s no built-in solution at this time though the workaround in the Appendix is straight forward.

尽管附录中的解决方法很简单，但由于目前没有内置解决方案，因此我将进一步详细介绍高可用性。

许可限制 (Licensing restrictions)

Although the data gateway application itself is free to download and use, there are licensing considerations when using some functionality, such as Live/DirectQuery, specifically to Analysis Services which I’ve summarised below.

尽管数据网关应用程序本身可以免费下载和使用，但是在使用某些功能（例如Live / DirectQuery，特别是Analysis Services时，需要考虑许可问题），我在下面对此进行了总结。

A full list of data sources that can use Live/DirectQuery connections can be found here.

可以在此处找到可以使用Live / DirectQuery连接的数据源的完整列表。

With the recent announcement of PowerBI Premium licensing and changes to the Pro & Free tiers, DirectQuery data from SSAS is now considered a “Pro” feature & will require a Pro or premium license*. More details on the tier restrictions can be found here.

随着最近宣布的PowerBI Premium许可和对Pro＆Free层的更改，来自SSAS的DirectQuery数据现在被视为“ Pro”功能，并且需要Pro或Premium许可证*。 有关层级限制的更多详细信息，请参见此处 。

*I’ve added an asterisk here as I think this will change. Microsoft seems to have forgotten small/medium businesses with the new model. There is also talk of a revision of the licensing tiers in PowerBI. Looking at Power BI Ideas, some form of change is at least top of the “Hot Ideas” list!

*我在这里添加了一个星号，因为我认为这将会改变。 微软似乎已经忘记了使用新模型的中小型企业。 也有谈论修订PowerBI中的许可层。 从 Power BI Ideas 来看，某种形式的更改至少是“ Hot Ideas”列表的顶部！

认证方式 (Authentication)

When connecting to on-premises databases you’ll generally connect with your Windows AD account or some kind of SQL/Service account, depending on the actual source. The former gives you the use of AD group security, single sign-on & allowing you to tailor the permissions for different sets of users. I.e. Sales Teams, Finance, Management etc.

连接到本地数据库时，通常将连接Windows AD帐户或某种SQL / Service帐户，具体取决于实际来源。 前者使您可以使用AD组安全性，单点登录并允许您为不同的用户组定制权限。 即销售团队，财务，管理等。

Using the latter gives flat access to your data, with no per-user restrictions. That can however, be achieved by multiple service accounts for different business units, teams etc.

使用后者可以对您的数据进行统一访问，而不受每个用户的限制。 但是，可以通过针对不同业务部门，团队等的多个服务帐户来实现。

With the On-premises data gateway, you provide a static/service account to connect to each data source. This can be an AD account (if using Windows authentication method) or a service account as described above (using Basic authentication)

使用本地数据网关，您可以提供一个静态/服务帐户来连接到每个数据源。 这可以是AD帐户（如果使用Windows身份验证方法）或如上所述的服务帐户（使用基本身份验证）

However, only an SSAS data source will allow “pass through authentication” from PowerBI, similar to Kerberos. All other data sources, (including SQL Server at this point) will also use the provided “service account” for data access.

但是，只有SSAS数据源将允许PowerBI进行“通过身份验证”，类似于Kerberos。 所有其他数据源（此时包括SQL Server）也将使用提供的“服务帐户”进行数据访问。

You could look at implementing row-level security to improve the security model but that has its own performance drawbacks. Another option would be multiple data sources within the data Gateway, pointing to the same database but using different accounts, a unique data source entry point for each group of users. This wouldn’t be the easiest to administer but you could implement a form of “team level” security this way.

您可以考虑实现行级安全性以改善安全性模型，但这有其自身的性能缺陷。 另一个选择是数据网关内的多个数据源，它们指向同一数据库但使用不同的帐户，这是每组用户的唯一数据源入口点。 这并不是最容易管理的方法，但是您可以通过这种方式实现“团队级别”安全性。

There is hope on the horizon though, Adam Saxton (@guyinacube) is aware of “pass through authentication” being worked on for SQL Server & there was a call to users with Kerberos implemented on an Oracle data source in the recent March blog update to help with testing.

但是，在地平线上还是有希望的，Adam Saxton（@guyinacube）意识到SQL Server正在使用“通过身份验证”，并且在3月的最新博客更新中 ，有人呼吁在Oracle数据源上使用Kerberos的用户帮助测试。

We need Volunteers!

我们需要志愿者！

If you’re using an Oracle data source with your on-premises data gateway in an environment where you have Kerberos configured, leave a comment here, we’re looking for candidates for a private preview we’re running.

如果在配置了Kerberos的环境中将Oracle数据源与本地数据网关一起使用，请在此处留言，我们正在寻找正在运行的私有预览的候选人。

I reference Adam Saxton a lot in this article as he’s been my primary source for new information & techniques to get what I need out of PowerBI & the data gateway. Most of his walkthroughs also detail the relevant PowerShell commands which are great for automation.

我在本文中经常引用Adam Saxton，因为他一直是我获取新信息和技术以从PowerBI和数据网关中获取所需信息的主要来源。 他的大多数演练还详细介绍了适用于自动化的相关PowerShell命令。

Also keep an eye out on Power BI Ideas for user opinions & updates on feature requests. You can also vote on ideas to raise their awareness.

另外，请密切注意Power BI Ideas的用户意见和功能要求的更新。 您也可以对创意进行投票以提高其知名度。

数据刷新 (Data Refresh)

This is another aspect of PowerBI & the data gateway that is affected by licensing & there are numerous restrictions that affect all data sources (not just on-premises data). It’s worth noting that the licenses described below are required to both consume & create reports.

这是PowerBI和受许可影响的数据网关的另一方面，并​​且有许多限制会影响所有数据源（不仅限于本地数据）。 值得注意的是，使用和创建报告都需要以下所述的许可证。

Requires a PowerBI Pro (Or Premium) License:

需要PowerBI Pro（或高级）许可证：

• (This is even capped at 8x a day for all license tiers!) （所有许可证级别的刷新率每天甚至上限为8倍！）

For restrictions specific to On-premises data, the following require a PowerBI Pro (Or Premium) License:

对于特定于本地数据的限制，以下内容需要PowerBI Pro（或Premium）许可证：

• ALL On-premises data that has any scheduled refresh will require a PowerBI Pro license. 具有任何计划的刷新的所有本地数据都需要PowerBI Pro许可证。

安装与设置 (Installation & Set up)

There is a great step by step guide over at the Microsoft PowerBI documentation, on setting up the data gateway in both “Enterprise” and personal modes so I won’t go through the basics here. As the data gateway is connecting to external resources you will likely run into firewall, ACL or configuration issues during set up. Thankfully there’s also a great troubleshooting guide, again over at the PowerBI documentation. I can’t really add anything to what’s described on that page. It actually touches on quite a few of the points I detail below.

在Microsoft PowerBI文档中有一个很好的分步指南，涉及在“企业”模式和个人模式下设置数据网关的问题，因此在这里我将不介绍其基本知识。 当数据网关连接到外部资源时，您可能会在设置过程中遇到防火墙，ACL或配置问题。 值得庆幸的是 ，在PowerBI文档中，还有一个出色的故障排除指南 。 我真的无法在该页面上添加任何内容。 它实际上涉及我在下面详述的许多要点。

Adam Saxton (@Guyinacube) also summarized his troubleshooting steps at SQLBits this year:

Adam Saxton（@Guyinacube）还总结了他今年在SQLBits上进行故障排除的步骤：

1. Latest version of the gateway 最新版本的网关
2. Check Refresh History 检查刷新历史
3. Errors in the Event logs 事件日志中的错误
4. Trace logs for the gateway 网关的跟踪日志
5. Performance counters 绩效柜台
6. Proxy configuration 代理配置
7. Fiddler – track HTTPS traffic 提琴手–跟踪HTTPS流量
8. Troubleshooting articles 故障排除文章

障碍与陷阱 (Roadblocks & Pitfalls)

There are a few hurdles you’ll come across on the road to publishing PowerBI reports with on-premises datasets. This list is not exhaustive but will hopefully help you avoid hours of fault finding & repeated work. I’m also hoping most of these will be irrelevant with future updates. Fingers crossed!

在使用本地数据集发布PowerBI报表的过程中，您会遇到一些障碍。 该列表并不详尽，但希望能帮助您避免数小时的故障查找和重复工作。 我也希望其中大多数与将来的更新无关。 手指交叉！

PowerBI桌面 (PowerBI Desktop)

• Data Connectivity Mode 数据连接模式选项

There is an informational message explaining you can’t choose both types for a single PBIX file but what it doesn’t explain is that if you select Import, and then spend hours sourcing data, building out the report you cannot then change the data source to DirectQuery. If you had initially chosen DirectQuery then it is ok to revert to Import. It simply does not allow the change from Import to DirectQuery. This applies to Analysis Services too so plan ahead.

有一条提示性消​​息，说明您不能为单个PBIX文件选择两种类型，但不能解释的是，如果选择Import ，然后花费数小时寻找数据，构建报告，则您将无法更改数据源。到DirectQuery 。 如果最初选择DirectQuery，则可以恢复为Import。 它根本不允许从Import更改为DirectQuery。 这也适用于Analysis Services，因此请提前计划。

Another restriction in PowerBI desktop crops up when using multiple data sources in a PBIX file, all of these must be added to the Gateway & be working for ANY of them in a PBIX to work.

当在PBIX文件中使用多个数据源时，PowerBI桌面的另一个限制出现了，所有这些数据源都必须添加到网关中，并且在PBIX中可以正常使用。

ODBC数据源命名 (ODBC Data Source Naming)

When dealing with an ODBC Data source type, you MUST ensure that the name of the Gateway data source matches the ODBC connection name EXACTLY. This is also case sensitive.

处理ODBC数据源类型时， 必须确保网关数据源的名称与ODBC连接名称完全匹配。 这也是区分大小写的。

It’s also worth noting that at this time that an ODBC connection, set up on your Gateway server is the best way to connect to other cloud services such as AWS. I hope we will see direct connectivity in the future though.

还需要注意的是，此时，在网关服务器上设置的ODBC连接是连接到其他云服务（例如AWS）的最佳方法。 我希望我们将来会看到直接连接。

数据网关凭证加密 (Data Gateway Credential encryption)

1. Data sources added to the Gateway will have both the username & password obfuscated (as they are both encrypted) in the Manage Gateway screen so make a note of which account you’ve used. Once you save it you cannot view it again, only update it. 添加到网关的数据源将在“管理网关”屏幕中同时混淆用户名和密码（因为它们均已加密），因此请记下您使用的帐户。 保存后，将无法再次查看，只能对其进行更新。

Analysis Services身份验证 (Analysis Services Authentication)

Coming back to Authentication, when using an Analysis Services data source which allows pass through authentication, PowerBI will connect to the SSAS instance using the stored “service account” but will authenticate the user using their UPN (User Principal Name). This is where you may run into problems. Your UPN is taken from the account you use to login to PowerBI & this must be the same as your AD login (e.g. Your network login) or the authentication will fail. Here’s a quick flow of what that looks like:

回到身份验证，当使用允许通过身份验证的Analysis Services数据源时，PowerBI将使用存储的“服务帐户”连接到SSAS实例，但将使用其UPN（用户主体名称）对用户进行身份验证。 这是您可能会遇到问题的地方。 您的UPN来自您用于登录PowerBI的帐户，该帐户必须与您的AD登录名（例如，您的网络登录名）相同，否则身份验证将失败。 这是一个快速的流程：

Sometimes these 2 credentials will never match (use of subdomains for example) so Microsoft have created a mapping process that will allow limited substitution/replacement of credentials passed through to Analysis Services & a quick test box to make sure it works.

有时，这2个凭据将永远不匹配（例如，使用子域），因此Microsoft创建了一个映射过程，该过程将允许有限的替换/替换传递给Analysis Services的凭据以及一个快速测试框，以确保其正常运行。

This setting alters the authentication process as described below, resulting in a match.

此设置如下所述更改身份验证过程，从而导致匹配。

Unfortunately there’s no ability to add a blanket regex for all users with the Map Username feature (if, for example your business uses a standard username convention). You can however substitute domains. I.e.

不幸的是，您无法使用“ 地图用户名”功能为所有用户添加通用正则表达式（例如，如果您的公司使用标准的用户名约定）。 但是，您可以替换域。 即

There’s some further documentation on UPN mapping over at Microsoft alongside a great video by Adam Saxton:

在Microsoft上还有一些有关UPN映射的更多文档，以及Adam Saxton的精彩视频：

Article: Manage your data source – Analysis Services

文章： 管理数据源– Analysis Services

Video: User Principal Name (UPN) Mapping in Power BI

视频： Power BI中的用户主体名称（UPN）映射

A more robust solution is to liaise with your Azure Active Directory admins and have them sync your normal AD account up to AAD. This will carry the correct UPN which will usually take the format username@company.com. This means no mapping is required.

一个更强大的解决方案是与您的Azure Active Directory管理员联系，并让他们将您的普通AD帐户同步到AAD。 这将带有正确的UPN，该格式通常采用username@company.com格式。 这意味着不需要映射。

灾难恢复/高可用性 (Disaster Recovery/High Availability)

As per the main PowerBI documentation, this is “in the roadmap” which has been the party line for as long as I recall. Fortunately there is a very simple workaround that I’ve detailed in the Appendix at the end of this post. It’s a manual workaround and assuming your databases are still online or retain their DNS records it should have your data gateway back online in minutes.

根据PowerBI的主要文档，在我看来，这是“路线图”，一直以来都是党的路线。 幸运的是，有一个非常简单的解决方法，我将在本文末尾的附录中进行详细介绍。 这是一种手动解决方法，并且假设您的数据库仍处于联机状态或保留其DNS记录，则应在数分钟内使数据网关重新联机。

监控与诊断 (Monitoring & Diagnostics)

Upon installing the data gateway a collection of perfmon counters are added to the local system, to monitor such metrics as:

安装数据网关后，会将性能计数器集合添加到本地系统，以监视以下指标：

• No. of failed queries 查询失败的数量
• No. of query executions/sec 查询执行次数/秒
• No. of connections 连接数
• Etc. 等等。

There was a great blog post by Brett Powell linked to in the PowerBI August update last year that goes into detail on how to set up these counters alongside system counters like CPU, memory, network throughput & pull these back into PowerBI. Having implemented it myself I highly recommend checking it out: MONITOR ON-PREMISES DATA GATEWAYS

Brett Powell在去年的PowerBI八月更新中链接了一篇很棒的博客文章，其中详细介绍了如何在系统计数器（如CPU，内存，网络吞吐量）以及如何将这些计数器设置到PowerBI中。 我自己实施了它，我强烈建议您检查一下： MONITOR预置数据网关

Beyond the performance metrics in Perfmon the data gateway application itself has a log output. This can be found here:

除了Perfmon中的性能指标之外，数据网关应用程序本身还具有日志输出。 可以在这里找到：

C:\Users\PBIEgwService\AppData\Local\Microsoft\On-premises data gateway

C：\ Users \ PBIEgwService \ AppData \ Local \ Microsoft \本地数据网关

If your data gateway is running under a domain account you should substitute the PBIEgwService in the above path. The logs can also be accessed from Event Viewer under Application and Services Logs

如果您的数据网关在域帐户下运行， 则应在上述路径中替换PBIEgwService 。 还可以从“事件查看器”的“ 应用程序和服务日志”下访问日志。

Opening up the log files you can see a lot of information being logged. There are a lot of undocumented GUIDs and recurring codes in the log files but it does appear to reliably capture data source and user errors if you strip out informational records. You can also increase logging to verbose to include query start and finish entries etc. The troubleshooting article I mention earlier goes into some detail on common Activity types & how to identify query durations from the Gateway log. A typical log error output looks like this:

打开日志文件，您可以看到许多信息正在被记录。 日志文件中有许多未记录的GUID和重复代码，但如果您除去信息记录，它确实可以可靠地捕获数据源和用户错误。 您还可以将日志记录增加为冗长，以包括查询开始和完成条目等。我前面提到的疑难解答文章详细介绍了常见的活动类型以及如何从网关日志中识别查询持续时间。 典型的日志错误输出如下所示：

Looking closer at the opening lines on such an error breaks down into components. Some of these are identified below:

仔细查看此类错误的开头行，可以分解为多个组件。 其中一些识别如下：

There is a full PowerBI admin portal built into Azure for viewing Usage metrics, audit logs & managing users. The catch is that you need to be an Azure Global Admin or be assigned the PowerBI Service admin role by a global admin to use it. This isn’t always easy to obtain.

Azure内置了一个完整的PowerBI管理门户，用于查看使用情况指标，审核日志和管理用户。 问题在于您需要是Azure Global Admin或由全局管理员分配给PowerBI Service管理员角色才能使用它。 这并不总是容易获得的。

Even with that level of access a lot of PowerBI and the data gateway itself is still a black box compared to what you may be used to with on-prem services like SQL & SSRS. This should improve over time but if you’ve used any other cloud services, some control always needs to be relinquished.

即使具有这种访问级别，与您可能习惯使用SQL和SSRS等本地服务相比，许多PowerBI和数据网关本身仍然是一个黑匣子。 随着时间的推移，这种情况应该会有所改善，但是如果您使用了其他任何云服务，则始终需要放弃一些控制权。

Keeping an eye on Adam Saxton’s YouTube channel & the PowerBI blog updates is the best way to keep up to date with new features & techniques.

密切关注Adam Saxton的YouTube频道和PowerBI博客更新是与新功能和新技术保持同步的最佳方法。

参考资料 (References)

• On-Premises Data Gateway 本地数据网关
• Data Gateway Data Sources 数据网关数据源
• PowerBI Licensing restrictions PowerBI许可限制
• PowerBI Ideas site PowerBI Ideas网站
• Data Gateway Troubleshooting 数据网关故障排除
• PowerBI Blog (March 2016) PowerBI博客（2016年3月）
• Data Gateway User Mapping 数据网关用户映射
• User Mapping video demo 用户映射视频演示
• PowerBI Blog (August 2016) PowerBI博客（2016年8月）
• Brett Powell blog article Brett Powell博客文章
• Adam Saxton’s YouTube Channel 亚当·萨克斯顿（Adam Saxton）的YouTube频道
• PowerBI Blog PowerBI博客

附录–灾难恢复解决方法 (Appendix – Disaster Recovery Workaround)

The following steps will demonstrate the “mock failover” of the On-premises data gateway.

以下步骤将演示本地数据网关的“模拟故障转移”。

1. Install the data gateway on a server (E.g. cpGATEWAY01) referring to the PowerBI documentation if required.

   如果需要，请参考PowerBI文档将数据网关安装在服务器上（例如cpGATEWAY01）。

2. Login with a PowerBI account & confirm successful connection to PowerBI.

   使用PowerBI帐户登录并确认成功连接到PowerBI。

3. Choose to Register a New Gateway

   选择注册新网关

4. You will be prompted for a Recovery Key. You MUST make a note of this. It is key to this process.

   系统将提示您输入恢复密钥。 您必须对此进行记录。 这是此过程的关键。

The Gateway is now setup on a single server.

现在，网关已在单个服务器上设置。

1. Install the data gateway on a second server. (E.g. cpGATEWAY_DR)

   在第二台服务器上安装数据网关。 （例如cpGATEWAY_DR）

2. Login with a PowerBI account & confirm successful connection to PowerBI.

   使用PowerBI帐户登录并确认成功连接到PowerBI。

3. Now choose to Migrate, restore or takeover an existing Gateway

   现在选择迁移，还原或接管现有网关

   

4. Pick the name of the Gateway from the drop down list. NOTE: The user you’re setting this up with must be an administrator of the Gateway you are restoring.

   从下拉列表中选择网关的名称。 注意：与此用户一起设置的用户必须是要还原的网关的管理员。

5. Enter the Recovery Key.

   输入恢复密钥。

6. The Gateway setup should complete successfully and you should see a screen similar to the following:

   网关设置应该成功完成，并且您应该看到类似于以下内容的屏幕：

   
7. You can now repeat steps 6-9 on your original Gateway (cpGATEWAY01) installation to move ownership back. It’s that simple! 现在，您可以在原始网关（cpGATEWAY01）上重复步骤6-9，以移回所有权。 就这么简单！

翻译自: https://www.sqlshack.com/considerations-for-on-premises-data-in-powerbi/

powerbi发布本地