Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

10
  • I think we need a bit more details : the query will obvisouly run against thousands of records, but what do the user get ? A grid with rows that you can load only partially and get the rest on the fly ? A report generated with all the data ? And does the complexity of the requests is high enough to eventually rely only on raw SQL or are you sure LINQ and not too complex queries will do the job ? Commented May 16, 2018 at 11:22
  • 1
    No answer to your question, but it is wrong that you can't test stored procedures. For example, in some companies their ETL resides mostly inside the database and is done with stored procedures. You can bet they are tested as well. Just directly on the database with SQL code (for example). Commented May 16, 2018 at 11:22
  • 1
    It is in fact possible to unit test stored procedures in SQL Server Commented May 16, 2018 at 11:57
  • But that aside, I suspect the bottleneck will be getting the data over to the mid tier or wherever you're going to be doing your number crunching. Commented May 16, 2018 at 12:07
  • Few users doing heavy queries to a grid does not sound like a big problem. I would try to make a naive implementation and make certain the grid supports paging. It also sounds like you can read uncomitted. I would also not use stored procedures, and my personal experience is that linq to entities is faster in .net core than 4.6 Commented May 16, 2018 at 12:10