How do I fetch sql data (including linked data 1-*) using entity framework

See more:

SQL

LINQ

C#5.0

EF6.0

Hi,

I am connected to my db via LINQ to SQL dbml objects. When I search for customers I need to get several linked tables too.
These include things like Payment Details, contact history, claim history etc...

I use paging so my data sets won't ever be very big. I would like to get all the data in one hit, but If I can't do it then I'll just have to get the results individually. This isn't a huge issue but it does make my save and edit features much more complex.

I need the result to be IQueryable as this is how my paging, filtering and sorting works. If I use a Stored Proc. then I would have to reverse engineer those to be used as parameters, and that way much messiness lies :S

Am I even making sense at this point? Maybe too much coffee for a friday :S

Thanks ^_^
Andy

---

PS: Some obligatory code

// details is my object that contains all of the editable data.  It is passed to each control so they can fill in their controls.
var data = details.PaymentDetails;
//The linked table objects have Data and Total used for paging.  Page size and index is dictated by the grid

var pageSize = 5,
    sort = user.settings.PaymentDetails.Sort, // default []
    group = user.settings.PaymentDetails.Group,// default []
    filter = user.settings.PaymentDetails.Filter,// default []
    columns = user.settings.PaymentDetails.Columns// default PaymentType, Status
//This is for those familiar with Kendo controls
var dataSource = new kendo.data.DataSource({
    data: data,
    schema: {
                total: "Total",
                data: "Data",
                model: {
                    id: "Id"
             },
    serverPaging: true,
    serverFiltering: true,
    serverSorting: true,
    pageSize: pageSize,
    sort: sort,
    filter: filter,
    group: group
});

Some exposition, as if you really care :P
The idea is that the main control (CustomerManagement) that contains these tabs child controls (CustomerDetails., PaymentDetails. etc) will check the changes against the original values. The last tab control is SaveChanges which summarizes the changes letting the user know which changes require Admin authorization etc, and what actions are available after the new details are in the system.
Oh, this section is for our Agents (telephone operators) to use. It has to be fast (signalr), dynamic (interlinked with every other agent currently logged in, again: signalr), and be fraud resistant; hence why i won't let users change payment details without authorization.