SSIS 2012 Project Deploymeny Progressively Slower

Question

I've noticed a gradual increase in the amount of time it takes for me to deploy a project to the SSIS Catalog. First of all, is there a way to deploy only specific packages or do I need to deploy the project everytime a package is added or changed?
In the beginning, the project only had few packages and the deployment time was not noticiably slow. Now, as I've added more projects (currently upto like 15 packages) I am beginning to notice an increase in the amount of time it takes for the project to
get deployed (like 5 minutes or more.)
Any explanation for this and how to make it go faster?

Answer 1

Hi All
I too am experiencing this exact same problem and have tried all suggestions listed so far, nothing stood out. I'm running SQL 2012 SP1 with CU3 or 4 (whichever is the one with the PowerView MD update!!) which I hoped would fix this issue which is really
starting to bug me, despite loving the new deployment method.
The only thing that made a small difference was adding several suggested missing indexes on the SSISDB database itself (see
http://www.ssistalk.com/2013/01/31/ssis-2012-catalog-indexing-recommendations/), however this increased the speed of the 'Changing protection level' but made no difference with the speed of the 'Deploying project' which used to be super fast, now I deploy
projects which used to deploy fast with say 2 or 3 small packages no take 15 or 20 minutes - come on Microsoft!!!!
I can only think that this is a bug of some kind or there is another index required somewhere on the SSISDB database, hopefully this will be something fixed in another CU or SP2 maybe whenever that arrives. I'll keep searching but let us know if you find
any fix for this too! :-)
Edit: Forgot to mention that I'm running with full admin rights on server and SQL server itself. It makes no difference running from server or remote workstation. This is NOT a network issue. I feel that its most likely an index required somewhere...
Further update: I've been taking a look at the activity monitor which is showing a suspended execute (detail: SSISDB.catalog.start_execution;1) and also it is having a problem with this select query:
SELECT
u.name AS [Name],
u.principal_id AS [ID],
ISNULL(ak.name,N'') AS [AsymmetricKey],
ISNULL(cert.name,N'') AS [Certificate],
ISNULL(suser_sname(u.sid),N'') AS [Login],
        CASE
        WHEN N'C' = u.type THEN 1
        WHEN N'K' = u.type THEN 2       
        WHEN N'S' = u.type AND SUSER_SNAME(u.sid) is null AND u.authentication_type != 2 THEN 3
        ELSE 0 END
       AS [UserType]
FROM
sys.database_principals AS u
LEFT OUTER JOIN sys.asymmetric_keys AS ak ON ak.sid = u.sid
LEFT OUTER JOIN sys.certificates AS cert ON cert.sid = u.sid
WHERE
(u.type in ('U', 'S', 'G', 'C', 'K'))
ORDER BY
[Name] ASC
And also this query seems to flick between suspended and running (wait type is still making me thing some indexing problem but I've checked existing ones and I've rebuilt several with high fragmentation and no difference):-
(@_msparam_0 nvarchar(4000),@_msparam_1 nvarchar(4000))SELECT
u.name AS [Name],
u.principal_id AS [ID],
CAST(CASE WHEN u.principal_id < 5 OR u.principal_id = 16382 OR u.principal_id = 16383 THEN 1 ELSE 0 END AS bit) AS [IsSystemObject],
CASE WHEN N'U' = u.type THEN 0 WHEN N'G' = u.type THEN 1 WHEN N'S' = u.type THEN 2 WHEN N'C' = u.type THEN 3 WHEN N'K' = u.type THEN 4 END AS [LoginType],
CAST(CASE dp.state WHEN N'G' THEN 1 WHEN 'W' THEN 1 ELSE 0 END AS bit) AS [HasDBAccess],
u.sid AS [Sid],
u.create_date AS [CreateDate],
u.modify_date AS [DateLastModified],
ISNULL(u.default_schema_name,N'') AS [DefaultSchema],
ISNULL(cert.name,N'') AS [Certificate],
ISNULL(ak.name,N'') AS [AsymmetricKey],
ISNULL(suser_sname(u.sid),N'') AS [Login],
ISNULL(u.default_language_lcid, -1) AS [DefaultLanguageLcid],
ISNULL(u.default_language_name,N'') AS [DefaultLanguageName],
u.authentication_type AS [AuthenticationType],
        CASE
        WHEN N'C' = u.type THEN 1
        WHEN N'K' = u.type THEN 2       
        WHEN N'S' = u.type AND SUSER_SNAME(u.sid) is null AND u.authentication_type != 2 THEN 3
        ELSE 0 END
       AS [UserType]
FROM
sys.database_principals AS u
LEFT OUTER JOIN sys.database_permissions AS dp ON dp.grantee_principal_id = u.principal_id and dp.type = @_msparam_0
LEFT OUTER JOIN sys.certificates AS cert ON cert.sid = u.sid
LEFT OUTER JOIN sys.asymmetric_keys AS ak ON ak.sid = u.sid
WHERE
(u.type in ('U', 'S', 'G', 'C', 'K'))and(u.name=@_msparam_1)
The packages and project at this point seem to be deployed as the appear in the Integration Services Catalog, just seems like these last processes are causing the deployment to take MUCH longer than appears... Is anyone else getting this in their slow deployments?