In general which is better performing in cases where both can be used. I noticed ServerSide is defaulted so it's easy to assume thats better.

ServerSide paging is better.

ClientSide Paging pulls all records from the database. While (as you may have giessed now) server side only pulls the specified page from the database.

Client side pulls all rows from the db till the page to read is read. So if you're fetching page 3 in a 10 million row table, you won't be pulling 10 million rows to the client, though you will read 3* the page size of rows.

Hmm, I just want to double check my senerio then.

Im in a self-servicing situation.

I'm using a LLBLGENPRO Datasource bound to an EntityCollection that has fields mapped on related fields.

The LLBLGENPRO Datasource is bound to a gridview with sorting and paging enabled.

The only way to enable sorting on a field mapped on relation is to enable ClientSide sorting on the LLBLGENPRO Datasource?

The only way to enable sorting on a field mapped on relation is to enable ClientSide sorting on the LLBLGENPRO Datasource?

Please read the following thread: http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=8219

And for sorting on a custom property, please read the following thread: http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=13171