I am working on a large tables (10 million records) project on MS SQL server and asking us to It is necessary to sort out the results on different areas with a very complex filter (which is 10+ column duration) and user selection on the UI.
There is a bit slow speed in running the questions, because we need to temporarily filter all the tables inside our stored procs and sorting.
I am thinking that I can use a process that loads part of the table which we can query with Raven DB, actually replacing the stored SSL procs and indexed raven db layer Am
Do you think that I should spend more time to investigate why the stored procs are slow and adapt something, or do you think the Raven DB approach can give me more benefits?
It seems as if you have a lot of complexity and uppercase in its architecture. Introduction of a new technology is unlikely to reduce the amount of complexity, so I certainly think that you should check the possibility of optimizing your current set up.
One thing you should see: Indexed View This allows you to create a query layer like the description, but working with the built-in SQL Server functionality should be very easy (if not much fun is!). .
Comments
Post a Comment