Where to draw the line between business logic and data access layer logic
===

The below Select statement lives in my data access layer a c# class:

    SELECT PreCondition, TestInstruction, ExpectedResult, ErrorText, TestState, TS.TeststepId, TS.CreatedAt FROM Unit U INNER JOIN TESTSTEP TS ON U.UnitId = @UnitId INNER JOIN TESTPLANTESTSTEP TPTS ON TPTS.TeststepId = TS.TeststepId AND TPTS.CreatedAt = TS.CreatedAt Where TPTS.TestplanId = @TestplanId

I do not have a business logic layer. The Select statement is directly called from an asp.net mvc controller:

ITestplanProvider.GetTeststeps(...)

Is joining these tables an expression of business logic? I do not want to put this stuff into the BLL another c# class and do the joining of the id`s and filtering of data in code thats slow as hell.

Do I something wrong?

