Forum Discussion
OLE DB or ODBC error: [DataSource.Error]
Hi,
I tried changing the parameters previously and it didn't work.
However, I did a workaround on it. My query was merged with another table and that seems to be causing the error. Hence, instead of using merge, I did a LOOKUPVALUE function in the table instead to get the columns I needed and that seems to work out just fine. Not sure why the merge would cause the error, but LOOKUPVALUE was the only workaround I could think of.
Thanks!
Hi Anonymous
I will give this a try and I will let you know if it works!
Thanks for the suggestion!
Daren
Hi Anonymous
Any updates on this thread?
If the error still exists, you can try playing with various options in the Sql.Database access data function in your power BI query.
Looking at the MSDN for this function https://msdn.microsoft.com/en-us/library/mt260902.aspx there are plenty of options to choose from. My favorite ones are CommandTimeout, MultiSubnetFailover and MaxDegreeOfParallelism.
MaxDegreeOfParallelism - degree of parallelism, that is the number of processors employed to run a single statement, for each query that has a parallel execution plan. There should be a server wide setting, however in some scenarios this might work as an overwrite.
MultiSubnetFailover- Is useful if you have an SQL Server Always On Availability cluseter. Here is what MSDN has to say about this option in the connection string:
"Always specify MultiSubnetFailover=True when connecting to a SQL Server 2012 availability group listener or SQL Server 2012 Failover Cluster Instance. MultiSubnetFailover enables faster failover for all Availability Groups and or Failover Cluster Instance in SQL Server 2012 and will significantly reduce failover time for single and multi-subnet AlwaysOn topologies. During a multi-subnet failover, the client will attempt connections in parallel. During a subnet failover, will aggressively retry the TCP connection."
Hi,
I tried changing the parameters previously and it didn't work.
However, I did a workaround on it. My query was merged with another table and that seems to be causing the error. Hence, instead of using merge, I did a LOOKUPVALUE function in the table instead to get the columns I needed and that seems to work out just fine. Not sure why the merge would cause the error, but LOOKUPVALUE was the only workaround I could think of.
Thanks!