May 20, 2015 at 1:24 pm
Hi,
I am seeing huge performance issue while executing SSIS package using SSISDB catalog option if I compare it with manual SSIS run using SQL data Tool.
As per support ticket (https://support.microsoft.com/en-us/kb/2972285), this was a known issue and fixed with service pack (SQL server 2012 - SP2). But, We already have latest build “cumulative update package 3” of SQL Server 2012 (released after SQL Server 2012 SP2) installed in our staging machine. But we do not see any major improvement in data load.
Please help in this?
Thanks
May 20, 2015 at 2:10 pm
First, I'm assuming that you actually use the right CU3 to SP2.
Then please allow me to ask : Have to performed ALL the steps given in KnowledgeBase article?
May 20, 2015 at 2:44 pm
Hi,
Yes, it is correctly installed.
Also, i have followed below steps as mentioned in KB article. But no success.
•Apply SQL Server 2012 SP2 on the SQL Server instance that is hosting SSISB catalog.
•Run the internal.cleanup_server_log stored procedure in the SSISDB to perform a full cleanup.
EXEC SSISDB.internal.cleanup_server_log
•Change the SSISDB database to single-user mode.
ALTER DATABASE SSISDB SET SINGLE_USER
•Call configure_catalog together with SEVER_OPERATION_ENCRYPTION_LEVEL parameter to change the operation log’s encryption level to PER_PROJECT (2) from the default of PER_EXECUTION (1).
EXEC SSISDB.catalog.configure_catalog @property_name='SERVER_OPERATION_ENCRYPTION_LEVEL',
@property_value='2'
•Change the SSISDB database back to multi-user mode.
ALTER DATABASE SSISDB SET MULTI_USER
•Run the internal.Cleanup_Server_execution_keys stored procedure to clean up transaction level keys.
EXEC SSISDB.internal.Cleanup_Server_execution_keys @cleanup_flag = 1
Regards
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply