Does Entity framework check for redundant OrderBy() methods - asp.net-mvc

Question

I have the following Repository model method:
public IQueryable<AccountDefinition> FindAccountDefinition(string q)
{
return entities.AccountDefinitions.Include(a => a.SDOrganization)
.Where (a=> String.IsNullOrEmpty(q) ||
a.ORG_NAME.ToUpper().StartsWith(q.ToUpper()))
.OrderBy(a=>a.ORG_NAME);
}
And the following action method:
[OutputCache(CacheProfile = "short", Location = OutputCacheLocation.Client,VaryByHeader="X-Requested-With", VaryByParam = "*")]
public ActionResult Index(string searchTerm=null, int page = 1)
{
//code goes here
var accountdefinition = repository.FindAccountDefinition(searchTerm== null ? null : searchTerm.Trim())
.OrderBy(a => a.ORG_NAME)
.ToPagedList(page, pagesize);
if (Request.IsAjaxRequest())
{
ViewBag.FromSearch = true;
return PartialView("_CustomerTable",accountdefinition);
}
return View(accountdefinition);
}
Currently I am doing the OrderBy(a => a.ORG_NAME) both inside the action method & inside the repository method. so how will entity framework and linq deal with this. I need to keep the OrderBy inside the repository method, since many other action methods are calling this repository method. and inside the action method I can not apply the ToPagedList unless I specify an OrderB. so my questions are:-
how will EF & linq deal with the duplicate OrberBy?
and will the OrderBy be done the DB level or on the server ?
Thanks
Edit
here is the generated sql statement from the sql profiler , and there is two OrderBy commands:-
exec sp_executesql N'SELECT TOP (15)
[Project1].[C1] AS [C1],
[Project1].[ORG_ID] AS [ORG_ID],
[Project1].[LOG_LOGO] AS [LOG_LOGO],
[Project1].[HEAD_LOGO] AS [HEAD_LOGO],
[Project1].[ORG_NAME] AS [ORG_NAME],
[Project1].[HASATTACHMENT] AS [HASATTACHMENT],
[Project1].[LOGIN_URI] AS [LOGIN_URI],
[Project1].[SUPPORT_EMAIL] AS [SUPPORT_EMAIL],
[Project1].[DEFAULTSITEID] AS [DEFAULTSITEID],
[Project1].[ORG_ID1] AS [ORG_ID1],
[Project1].[NAME] AS [NAME],
[Project1].[CREATEDTIME] AS [CREATEDTIME],
[Project1].[DESCRIPTION] AS [DESCRIPTION]
FROM ( SELECT [Project1].[ORG_ID] AS [ORG_ID], [Project1].[LOG_LOGO] AS [LOG_LOGO], [Project1].[HEAD_LOGO] AS [HEAD_LOGO], [Project1].[ORG_NAME] AS [ORG_NAME], [Project1].[HASATTACHMENT] AS [HASATTACHMENT], [Project1].[LOGIN_URI] AS [LOGIN_URI], [Project1].[SUPPORT_EMAIL] AS [SUPPORT_EMAIL], [Project1].[DEFAULTSITEID] AS [DEFAULTSITEID], [Project1].[ORG_ID1] AS [ORG_ID1], [Project1].[NAME] AS [NAME], [Project1].[CREATEDTIME] AS [CREATEDTIME], [Project1].[DESCRIPTION] AS [DESCRIPTION], [Project1].[C1] AS [C1], row_number() OVER (ORDER BY [Project1].[ORG_NAME] ASC) AS [row_number]
FROM ( SELECT
[Extent1].[ORG_ID] AS [ORG_ID],
[Extent1].[LOG_LOGO] AS [LOG_LOGO],
[Extent1].[HEAD_LOGO] AS [HEAD_LOGO],
[Extent1].[ORG_NAME] AS [ORG_NAME],
[Extent1].[HASATTACHMENT] AS [HASATTACHMENT],
[Extent1].[LOGIN_URI] AS [LOGIN_URI],
[Extent1].[SUPPORT_EMAIL] AS [SUPPORT_EMAIL],
[Extent1].[DEFAULTSITEID] AS [DEFAULTSITEID],
[Extent2].[ORG_ID] AS [ORG_ID1],
[Extent2].[NAME] AS [NAME],
[Extent2].[CREATEDTIME] AS [CREATEDTIME],
[Extent2].[DESCRIPTION] AS [DESCRIPTION],
1 AS [C1]
FROM [dbo].[AccountDefinition] AS [Extent1]
INNER JOIN [dbo].[SDOrganization] AS [Extent2] ON [Extent1].[ORG_ID] = [Extent2].[ORG_ID]
WHERE (#p__linq__0 IS NULL) OR (( CAST(LEN(#p__linq__0) AS int)) = 0) OR (( CAST(CHARINDEX(UPPER(#p__linq__1), UPPER([Extent1].[ORG_NAME])) AS int)) = 1)
) AS [Project1]
) AS [Project1]
WHERE [Project1].[row_number] > 0
ORDER BY [Project1].[ORG_NAME] ASC',N'#p__linq__0 nvarchar(4000),#p__linq__1 nvarchar(4000)',#p__linq__0=NULL,#p__linq__1=NULL

Answer 1

1) how will EF & linq deal with the duplicate OrberBy?
It will ignore the second OrderBy because the correct way to specify multiple ORDER BY clauses is to use OrderBy first and then use ThenBy
2) and will the OrderBy be done the DB level or on the server ?
At the DB level since you are applying it to the IQueryable<T> before calling ToPagedList which will execute the statement.

Answer 2

I suppose, you have to call OrderBy in your controller, because the ToPagedList method requires IOrderedQueryable instead of IQueryable as the parameter, so what about returning IOrderedQueryable<AccountDefinition> from your repository?
public IOrderedQueryable<AccountDefinition> FindAccountDefinition(string q) {
return entities.AccountDefinitions
.Include(a => a.SDOrganization)
.Where (a => String.IsNullOrEmpty(q) ||
a.ORG_NAME.ToUpper().StartsWith(q.ToUpper()))
.OrderBy(a=>a.ORG_NAME);
}
OrderBy returns IOrderQueryable by default, so there is no overhead and the other methods shouldn't be affected by this change.