Best way to load many rows on datagrid with MVVM?

Question

Hi,
I have a table with more than 2 million rows and 20 columns. of course this takes so long to load the data on datagrid and even mostly causing out of memory exception. what kind of way can I follow to load this dynamically and efficiently? 
In the attached project for example, in ordersview.xaml I am binding Orders as following. I guess that doing Async helps but not completly in my case. I need to find a kind of paging and background loading. Sample
project doesnt have so many data but if possible to presume that there are so many Orders and i want to load all data. 
<DataGrid Name="grdOrders" CopyingRowClipboardContent="DataGrid_CopyingRowClipboardContent" AutoGenerateColumns="False"
ItemsSource="{Binding Orders, IsAsync=True}"
protected async override void GetData( )
"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it."

Answer 1

I'll mention some complications first.
If you keep a context alive, by default it will have change tracking for anything you read using it.  This is irrelevant if you read like 20 records.  Once you start talking many thousands, this if an overhead you want to avoid.
A common dodge is to open a context, grab data, transform it elsewhere and then close the context.
Work with your data disconnected.
That means you lose change tracking but you can add such properties as IsDirty to a wrapping viewmodel so they each track their own changes.
This isn't just about highlighting changed fields:
https://gallery.technet.microsoft.com/WPF-Highlight-Changed-a77976d4
Another dodge is to start off knowing what the user is probably interested in.
I want todays newspaper, this months sales, yesterdays stock levels....
People rarely actually want totally flexible filtering.
Don't re-implement excel unless you really have to.
You can filter huge collections, but you nothing is fr and if you put enough data into a collection thiDSDngs will slow. Eventually.
But.  You can do date ranges.  Collectionview filtering can be persuaded to do pretty much anything you like by some variation of the filtering examples in those tips.
For example, each of those predicates in the list to check can be quite complicated and you could go with .Any rather than trueforall.
Hope that helps.
Recent Technet articles: Property List Editing;
Dynamic XAML