When deploying my SSAS solution I am getting error message: "The connection either timed out or was lost"

-

This document describes that one of the workarounds is to add ";SSPI=NTLM" or ";Integrated Security=SSPI" to the connection string. I found that doing that really helped.

Here are steps how to add additional parameter to the connection string for the BIDS environment:

·         In the BIDS environment select menu item "Project" and then "Properties"

·         Select "Deployment" tab

·         Change Target/Server property value from "YourServerName" to "YourServerName;SSPI=NTLM"

Comments

Post a Comment

Popular posts from this blog

Announcing backup and restore improvements for large datasets near the size limit

-
Image
In August 2021, we announced  general availability (GA) of backup and restore for large datasets . This Power BI feature closes an important gap to Azure AS. You can backup Power BI datasets on a regular basis to meet the data retention and disaster recovery requirements of your organization. You can also use this feature to migrate enterprise BI workloads from Azure AS to Power BI. Another common scenario is to roll back an existing Power BI dataset to a previous version. Yet, rolling back was not without challenges for large datasets near the max dataset size. But thanks to the latest improvements, you can now even restore a backup file when the dataset size is near the SKU limitation. You no longer need to be concerned that size limits impact restorability. For example, a P3 capacity has a max dataset size of 100 GB. If you wanted to maximize memory usage, you might have intended to host a dataset with 70 GB on this capacity. However, prior to the recent backup and restore improveme
Read more

Enhanced refresh with the Power BI REST API is now generally available

-
We’re excited to move Enhanced refresh with the Power BI REST API (formerly asynchronous refresh) from public preview to general availability in Power BI Premium, Power BI Premium per User, and Power BI Embedded. As noted in the public preview announcement, this feature not only eliminates the need for synchronous client connections to perform a refresh, but also unlocks enterprise-grade refresh capabilities. It’s a significant improvement over the standard refresh REST API in Power BI. By using the enhanced refresh REST API, you can leverage built in features for refresh management, reliability, and granularity as shown by the following examples. Cancel an in-progress refresh operation. Check the status of historical, current, and pending refreshes. Refresh individual tables and individual partitions. Batched commits with restarts so long refreshes do not need to start from the beginning in cases of transient failure. Application of incremental refresh policy. Control the Analysis Ser
Read more

What’s New in SQL Server 2014 since SQL Server 2008 R2

-
PERFORMANCE & SCALE o        In-Memory OLTP o        Enhanced In-Memory ColumnStore for DW o        Support for 640 logical proc. & 4 TB memory o        Support to 15,000 partitions o        Resource Governor IO governance o        Buffer Pool Extension to SSDs o        Query optimization enhancements o        SysPrep at cluster level o        Predictable performance with tiering of compute, network, and storage with Windows Server 2012 R2 HIGH AVAILABILITY o        SQL Server AlwaysOn o        Delayed Durability o        Recovery Advisor o        Windows Server Core o        Live Migration o        Online Operations enhancements o        Clustered Shared Volume support, VHDX support (Windows Server 2012 R2) o        Manage on-premises and cloud apps (System Center 2012 R2) SECURITY o        User-Defined Server Roles o        Default Schema for Groups o        SQL Server Audit o        SQL Server Fine-grained Auditing o        Enhanced separation of duty o        CC certificat
Read more