The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
The built in Snowflake connector does not work to import large tables. I'm just talking about modestly large, like 4 million rows.
There is some very old information out there about this from 2022 timeframe and the workaround from that instance is not valid in the current version of Power BI Desktop since the menus and options have changed since then.
It seems insane to me that this has been an ongoing issue with Power BI Desktop for 3+ years.
Any Microsoft superheros out there know if this will be addressed? It seems like my best option is to migrate to a different visualization tool.
Thanks so much! Error message in full is below:
Unexpected error: Index was outside the bounds of the array.
Details:
Microsoft.Mashup.Evaluator.Interface.ErrorException: Index was outside the bounds of the array. ---> System.IndexOutOfRangeException: Index was outside the bounds of the array. ---> System.IndexOutOfRangeException: Index was outside the bounds of the array.
at Microsoft.Mashup.Engine1.Library.Adbc.AdbcPageReader.AdbcPage.Fallback(IArrowArray arrowArray, Column column, Int32 offset, Int32 columnIndex)
at Microsoft.Mashup.Engine1.Library.Adbc.AdbcPageReader.AdbcPage.<>c__DisplayClass10_0.<.ctor>b__0(IArrowArray src, Column dest, Int32 offset)
at Microsoft.Mashup.Engine1.Library.Adbc.AdbcPageReader.AdbcPage.Read(RowRange rowRange, Int32 offset)
at Microsoft.Mashup.Engine1.Library.Adbc.AdbcPageReader.Read(AdbcPage page)
at Microsoft.Mashup.Engine.Interface.Tracing.TracingPageReader.Read(IPage page)
at Microsoft.Mashup.Common.IPageReaderExtensions.NotifyingPageReader.Read(IPage page)
at Microsoft.Mashup.Common.IPageReaderExtensions.NotifyingPageReader.Read(IPage page)
at Microsoft.Mashup.Engine1.Library.Adbc.AdbcDataSource.ExceptionHandlingPageReader.<>c__DisplayClass2_0.<Read>b__0()
at Microsoft.Mashup.Engine1.Library.Common.DbExceptionHandler.<>c__DisplayClass10_0.<InvokeWithoutRetry>b__0()
at Microsoft.Mashup.Engine1.Library.Common.DbExceptionHandler.RunWithRetryGuard[T](Int32 maxRetryAttempts, Func`1 action)
at Microsoft.Mashup.Engine1.Library.Common.DbExceptionHandler.Invoke[T](Int32 maxRetry, Func`1 action)
at Microsoft.Mashup.Engine1.Library.Common.DbExceptionHandler.InvokeWithoutRetry(Action action)
at Microsoft.Mashup.Engine1.Library.Common.ProgressPageReader.Read(IPage page)
at Microsoft.OleDb.Serialization.PageReaderDataReader.Read()
at Microsoft.Mashup.Engine1.Library.Common.DbData.CachingDbDataReader.<>c__DisplayClass48_0.<WrappedRead>b__0()
at Microsoft.Mashup.Engine1.Library.Common.DbData.CachingDbDataReader.TraceException(Func`1 tracer, Action action)
at Microsoft.Mashup.Engine1.Library.Common.DbData.CachingDbDataReader.WrappedRead()
at Microsoft.Mashup.Engine1.Library.Common.DbData.CachingDbDataReader.Read()
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at Microsoft.Mashup.Engine1.Runtime.SkipTakeEnumerator`1.MoveNext()
at Microsoft.Mashup.Engine1.Runtime.RetryQuery.RetryEnumerator.MoveNext()
at Microsoft.Mashup.Evaluator.SimpleDocumentEvaluator.ValuePreviewValueSource.TableValuePreviewValueSource.SerializeRows(Int32 count)
at Microsoft.Mashup.Evaluator.SimpleDocumentEvaluator.ValuePreviewValueSource.TableValuePreviewValueSource.get_SmallValue()
at Microsoft.Mashup.Evaluator.Interface.TracingPreviewValueSource.get_SmallValue()
at Microsoft.Mashup.Evaluator.RemotePreviewValueSource.<>c__DisplayClass0_0.<RunStub>b__0()
at Microsoft.Mashup.Evaluator.EvaluationHost.ReportExceptions(String entryName, IEngineHost engineHost, IMessageChannel channel, Action action)
--- End of inner exception stack trace ---
at Microsoft.Mashup.Evaluator.EvaluationHost.<>c__DisplayClass27_0.<TryReportException>b__1()
at Microsoft.Mashup.Common.SafeExceptions.IgnoreSafeExceptions(IEngineHost host, IHostTrace trace, Action action)
at Microsoft.Mashup.Evaluator.EvaluationHost.TryReportException(IHostTrace trace, IEngineHost engineHost, IMessageChannel channel, Exception exception)
at Microsoft.Mashup.Evaluator.EvaluationHost.ReportExceptions(String entryName, IEngineHost engineHost, IMessageChannel channel, Action action)
at Microsoft.Mashup.Evaluator.RemoteDocumentEvaluator.Service.<>c__DisplayClass12_0`1.<OnBeginGetResult>b__0()
at Microsoft.Mashup.Evaluator.EvaluationHost.ReportExceptions(IHostTrace trace, IEngineHost engineHost, IMessageChannel channel, Action action)
at Microsoft.Mashup.Evaluator.RemoteDocumentEvaluator.Service.OnBeginGetResult[T](IMessageChannel channel, BeginGetResultMessage message, Action`1 action)
at Microsoft.Mashup.Evaluator.RemoteDocumentEvaluator.Service.OnBeginGetPreviewValueSource(IMessageChannel channel, BeginGetPreviewValueSourceMessage message)
at Microsoft.Mashup.Evaluator.MessageHandlers.TryDispatch(IMessageChannel channel, Message message)
at Microsoft.Mashup.Evaluator.ChannelMessenger.ChannelMessageHandlers.TryDispatch(IMessageChannel channel, Message message)
at Microsoft.Mashup.Evaluator.MessageHandlers.Dispatch(IMessageChannel channel, Message message)
at Microsoft.Mashup.Evaluator.ChannelMessenger.OnMessageWithUnknownChannel(IMessageChannel baseChannel, MessageWithUnknownChannel messageWithUnknownChannel)
at Microsoft.Mashup.Evaluator.MessageHandlers.TryDispatch(IMessageChannel channel, Message message)
at Microsoft.Mashup.Evaluator.ChannelMessenger.ChannelMessageHandlers.TryDispatch(IMessageChannel channel, Message message)
at Microsoft.Mashup.Evaluator.MessageHandlers.Dispatch(IMessageChannel channel, Message message)
at Microsoft.Mashup.Evaluator.EvaluationHost.Run()
at Microsoft.Mashup.Container.EvaluationContainerMain.Run(Object args)
at Microsoft.Mashup.Evaluator.SafeThread2.<>c__DisplayClass9_0.<CreateAction>b__0(Object o)
at Microsoft.Mashup.Container.EvaluationContainerMain.SafeRun(String[] args)
at Microsoft.Mashup.Container.EvaluationContainerMain.Main(String[] args)
--- End of inner exception stack trace ---
at Microsoft.Mashup.Evaluator.EvaluationHost.OnException(IEngineHost engineHost, IMessageChannel channel, ExceptionMessage message)
at Microsoft.Mashup.Evaluator.MessageHandlers.TryDispatch(IMessageChannel channel, Message message)
at Microsoft.Mashup.Evaluator.MessageHandlers.Dispatch(IMessageChannel channel, Message message)
at Microsoft.Mashup.Evaluator.ChannelMessenger.ChannelMessageHandlers.TryDispatch(IMessageChannel channel, Message message)
at Microsoft.Mashup.Evaluator.MessageHandlers.Dispatch(IMessageChannel channel, Message message)
at Microsoft.Mashup.Evaluator.Interface.IMessageChannelExtensions.WaitFor[T](IMessageChannel channel)
at Microsoft.Mashup.Evaluator.RemotePreviewValueSource.PreviewValueSource.WaitFor(Func`1 condition, Boolean disposing)
at Microsoft.Mashup.Evaluator.RemotePreviewValueSource.PreviewValueSource.get_SmallValue()
at Microsoft.Mashup.Evaluator.Interface.TracingPreviewValueSource.get_SmallValue()
at Microsoft.Mashup.Host.Document.Analysis.PackageDocumentAnalysisInfo.PackagePartitionAnalysisInfo.SetPreviewValue(EvaluationResult2`1 result, Func`1 getStaleSince, Func`1 getSampled)
Solved! Go to Solution.
Hello @mickjaeger ,
Thank you for reaching out to Microsoft Fabric Community forum.
@Akash_Varuna Thank you for your quick response.
@mickjaeger Apologies for the inconvenience caused.
The error you reported is a known issue, and the Microsoft team is actively working on a resolution. In the meantime, please refer to the screenshot below for reference, along with the suggested workaround to address the issue.
Additionally, I have attached the supporting documentation for your further understanding.
Power Query Snowflake connector - Power Query | Microsoft Learn
Known issue - Snowflake Implementation="2.0" connector doesn't display views - Microsoft Fabric | Mi...
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos |
Regards,
B Manikanteswara Reddy
Hello @mickjaeger ,
Thank you for reaching out to Microsoft Fabric Community forum.
@Akash_Varuna Thank you for your quick response.
@mickjaeger Apologies for the inconvenience caused.
The error you reported is a known issue, and the Microsoft team is actively working on a resolution. In the meantime, please refer to the screenshot below for reference, along with the suggested workaround to address the issue.
Additionally, I have attached the supporting documentation for your further understanding.
Power Query Snowflake connector - Power Query | Microsoft Learn
Known issue - Snowflake Implementation="2.0" connector doesn't display views - Microsoft Fabric | Mi...
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos |
Regards,
B Manikanteswara Reddy
hello v-bmanikante!
thank you for helping with this frustrating issue. 🐛 It seems that removing the 'implementation = 2.0' was a workaround for a different issue (loading views) but it did help me to get through the import of my table. The issue documentation you shared also says the issue was fixed in May 2025, and I can confirm that I can load views so that part is true, but seems this issue I'm experiencing is different. However, the same workaround seems to work for me. I'm truly glad to know about this!
Thanks so much for the help!!! ✨
Hi @mickjaeger Ensure Power BI Desktop is updated to the latest version. Use query parameters to reduce data size or switch to Direct Query mode for handling large datasets dynamically. Optimize the Snowflake data with partitions or materialized views for smaller, summarized datasets.
Hello Akash! Thanks for the fast response!!! Of course I have Power BI Desktop updated to the latest version, that's something Microsoft excels at, install from the Microsoft Store and the software is automatically updated. I love this feature.
The challenge with this issue is that I can't get to Power Query where I would normally filter and reduce the dataset size. We have chosen to use the Import mode instead of direct query since this report only needs a daily refresh. And our Snowflake account is standard edition so we do not have access to materialized views.
I hope you have a wonderful day, thanks again!