Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

I am looking for a solution giving me automated archiving of SQL Server databases based on a smart interpretation of table relationships that is able to archive records from related tables minimizing (or making unnecessary) to write custom ETL code.

So far the only solution I have been able to find (by Google) is Informatica Data Archive

In the DataSheet I can read:

Smart Automated Partitioning: This edition automates database partitioning based on business entities, placing records from related tables in the same table space, not just individual tables. Your IT team can leverage underlying database partitioning functionality to manage both partitioning and archiving from a central console.

Sounds pretty much like what I am looking for...¿Are there any others like this from other vendors? According to this book there should be many tools offering this.. but I can not find anything...

If there is no other prepackaged solutions I would also be interested in information on how to build my own... (althought I realize it might not be feasible)

Basically I am looking for a tool that enables a developer to do this (obtained from here):

  1. The ETL developer defines the source and destination of the extraction process, including servers, relational databases, and tables.
  2. For each table, the schema (columns, index, and constraints) can either be automatically retrieved by the system or manually specified by the ETL developer.
  3. The ETL developer specifies the mapping between source and destination at the database, table, and column level.
  4. The ETL developer selects either a full or delta load.
  5. The ETL developer configures an orchestration process. For each table, ETL developers define one or multiple steps for performing the extraction.
  6. The ETL developer specifies how ETL packages should be executed—at a scheduled time or on demand.
  7. The system dynamically generates one or more SSIS packages.
  8. The system deploys the SSIS packages to a distributed execution environment.
  9. The system executes ETL jobs and captures the job status.

I found this abandoned opensource project: MDDE unfortunately it is also pretty much undocumented (this is the usage information I could find) unsupported and obsolete (apparently is designed to work only with SQL Server 2005 and I need something for SQL Server 2008 R2)

OTOH: I am surprised that there is no "archiving" tag in this site...

share|improve this question

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.