Friday, November 16, 2012 4:08 AM
My Clint has multiple SQL databases. The size of all databases are close to 55TB and the db volume is expected to grow 10-15% per month. So we are planning to maintain the data by implementing the Data LifeCycle Management (DLM).
Would like to know how to implement DLM using SQL Server 2012 with its in built features.
Is it possible to have such solution using sql 2012? and how can we have a solution to store the data on multi-tier storage model? (like high performance/medium performance/low performance disks) So that users will get even the historical data whenever they want along the recent data.
Thanks in advance.
- Edited by veeraghav Friday, November 16, 2012 4:10 AM
Friday, November 16, 2012 10:29 PM
You can achieve the objective and the benefits of ILM by using Database Archiving or implementing database archiving on SQLServer 2012. (As a disclaimer I work with Solix Technologies)
Solix EDMS Database Archiving solution does what you are looking for and works on SQLServer and other databases as well. Check out additional information at the following links.
You can contact us via http://www.solix.com/contact_us.htm
Saturday, November 17, 2012 5:42 AM
Thanks for your reply.
I have following questions ,
1) Reads the archived data whenever user tries to see data or he has to make request to Operation team to provide the archived data?
2) How much Hardware cost will reduce by implementing EDMS (with multi-tier storate) of Solix solution ? How it stores the active, less-active data and where it gets stored (interms of Hardware)?
Thanks in advance.
Monday, November 19, 2012 5:25 PM
For #1 - User doesn't have to request the archived data from ops team.
Solix EDMS provides 2 options (1) transparent data access via app interface (2) use Solix APM web access layer to get to archived data.
Transparent data access doesn't need change to application but needs understanding of application security deployed so that access to archiving data can be provisioned accordingly
For #2 - Hardware cost savings which includes cost to keep up hardware upgrades, new storage will depend upon the how much amount of data is modeled under archiving policies. The idea of ILM on top of pure storage management, goes beyond to maintain data growth in deployed at consistent rate, by moving the data, enforce retention polices so that data is maintained according to regulations and get better efficiencies around Backup and DR for better business continuity. Suggest to view some of the customer case studies in on demand webinars on solix.com to see how customers have deployed and benefits achieved.
For the second part of #2 - Solix EDMS uses the notion of creating complete business objects to wrap the data that is eligible for archiving based on retention policies and business criteria, and the data can be move to in-active database archive which is secondary instance of database where users can transaparent data access and again the data an moved on based on timelines to highly compressed archive where archived data can be accessed by Solix APM. Solix EDMS is agnostic of underlying hardware/storage and database, it is the policies that drive the movement of data accordingly to different layers of storage to eventual data destruction.