New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Archiving Yearly Sales #8030

asim-vax opened this Issue Jan 4, 2017 · 2 comments


None yet
2 participants

asim-vax commented Jan 4, 2017

To whom it may concern,

As our data grows(over 5 years worth of sales data) our sales_order (sales_flat_order table in M1) table is exponentially growing - trying to run queries against this is becoming slower. Is there a development path for something like sales_order_2014, sales_order_2015 or any sort of archiving of older data?




This comment has been minimized.

pboisvert commented Jan 20, 2017

this Github is for M2 issues. Your report appears to be against M1

@pboisvert pboisvert closed this Jan 20, 2017


This comment has been minimized.

asim-vax commented Jan 22, 2017

@pboisvert I was asking if there was a plan for something like this in M2? We are in the process of moving our site over from M1 to M2, and there is a huge amount of data in the table

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment