Timeline for Which is best software design for heavy query based app
Current License: CC BY-SA 4.0
18 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 16, 2018 at 12:55 | history | edited | X.Otano | CC BY-SA 4.0 |
added 301 characters in body
|
| May 16, 2018 at 12:33 | answer | added | Ewan | timeline score: 1 | |
| May 16, 2018 at 12:27 | comment | added | Robbie Dee | @Badulake Fair enough - it would certainly help with portability... | |
| May 16, 2018 at 12:22 | history | edited | X.Otano | CC BY-SA 4.0 |
added 125 characters in body
|
| May 16, 2018 at 12:20 | comment | added | X.Otano | @Walfrat queries are not too much complicated, just summarize the data, group by date(month,year) . Query items wih some characteristics. Multiple Joins are needed across multiple tables, that will be the worst scenario | |
| May 16, 2018 at 12:14 | comment | added | X.Otano | @RobbieDee i don´t want to redevelop the business rules each time i change the database engine. So i think stored procedures are not the best choice | |
| May 16, 2018 at 12:13 | history | edited | X.Otano | CC BY-SA 4.0 |
added 73 characters in body
|
| May 16, 2018 at 12:13 | comment | added | Robbie Dee | And there is PLINQ of course... | |
| May 16, 2018 at 12:13 | history | edited | X.Otano | CC BY-SA 4.0 |
added 73 characters in body
|
| May 16, 2018 at 12:12 | comment | added | X.Otano | @Walfrat I would prefer to use LINQ because the logic resides in the code, so I make it independent from database changes (for example oracle to sql server) .The problem is that maybe the joins & data its big enough to produce perfomance issues | |
| May 16, 2018 at 12:10 | comment | added | Thomas Koelle | 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 | |
| May 16, 2018 at 12:09 | history | edited | X.Otano | CC BY-SA 4.0 |
added 143 characters in body
|
| May 16, 2018 at 12:07 | comment | added | Robbie Dee | 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. | |
| May 16, 2018 at 12:00 | history | edited | Stephen C | CC BY-SA 4.0 |
Fixed spelling errors
|
| May 16, 2018 at 11:57 | comment | added | Robbie Dee | It is in fact possible to unit test stored procedures in SQL Server | |
| May 16, 2018 at 11:22 | comment | added | kutschkem | 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). | |
| May 16, 2018 at 11:22 | comment | added | Walfrat | 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 ? | |
| May 16, 2018 at 11:03 | history | asked | X.Otano | CC BY-SA 4.0 |