Saturday, November 27, 2010 12:22 PM
After many executions the [catalog].[operations] & [catalog].[executions] tables are going to get very very long and this *could* end up affectig ETL performance. it will definitely afffect performance of querying those tables.
Could you give us purge and archive abilities for those tables i.e. built-in purging/archiving mechanisms rather than simply manually moving data round.
P.S. I submitted this to Connect: https://connect.microsoft.com/SQLServer/feedback/details/625051/ssis-denali-need-ability-to-purge-archive-catalog-operations-catalog-executions#details but figured I'd raise it here to make sure it as noticed as early as possible.
http://sqlblog.com/blogs/jamie_thomson/ | @jamiet | About me
- Changed Type Jamie ThomsonMVP Wednesday, December 01, 2010 8:30 AM
Wednesday, December 01, 2010 1:43 AM
In Catalog's Properties dialog, could you find entries to enable cleaning logs periodically and to set the retention period? They are for your need.
This posting is provided "AS IS" with no warranties, and confers no rights.
- Marked As Answer by Jamie ThomsonMVP Wednesday, December 01, 2010 8:30 AM
Wednesday, December 01, 2010 8:30 AM