SQLBits 2023
Keeping historical data in tables forever – mission (im)possible!
Let’s discover some solutions for keeping historical data in the database when you receive near to impossible requirements like storing data in same tables forever and being able to edit and query them at the same time, of course keeping the response at its best. Based on a real project case the session walks you through the design process from the start to the reaching of the final solution and making the client (and developers) happy.
Data growth can easily become a problem soon after deploying a database in production, especially if data layout and data management was not planned. Let’s discover some solutions for keeping historical data in the database when you receive near to impossible requirements like storing data in same tables forever and being able to edit and query them at the same time, of course keeping the response at its best. Will combining partitioning, temporals, CSI, and other indexing with different loading/unloading/deletion make it possible? The session starts by defining the frame requirements coming from real projects and goes through different alternatives and possible solutions, their benefits, and drawbacks. Based on a real project case the session walks you through the design process from the start to the reaching of the final solution and making the client (and developers) happy.