1. Explore the Integration Services Catalog
By Fendy Huang
Blog:
This session, we are going to talk about IS catalog
Everything related to IS catalog

2. Agenda Overview Configure Integration Services Catalog
Explore the SSISDB DB Objects
Integration Services Dashboard
Change Logging Level/Permissions
Ways to Execute the SSIS Packages
Clean the Catalog Data
Create/Deploy Custom Reports
Q & A

3. SSIS Overview/ New concepts or features

4. What is new for SSIS 2012?
Project Deployment Model
SSIS Catalog

5. Compare the Deployment Model
Package Deployment
Project Deployment
Package is a unit of deployment
Project is a unit of deployment
Package Store: File System or MSDB database
Stored in SSISDB database
Packages executed wherever DTExec was called
Executions run on the server where the SSISDB catalog is stored.
DTExec /SQL
DTExec /DTS
DTExec /F
DTExec /ISSERVER

6. SSIS Catalog Stores packages, parameters, etc.
Stores multiple versions
Automatically log all operation activities

8. Steps to Create IS Catalogs
Open SQL Server Management Studio
Right click on the Integration Services node
Click on the Create Catalog…..
Create the Catalog need to be sysadmin
The catalog uses CLR stored procedures.

9. The catalog name is SSISDB.
Enter the password for encryption then hit the OK button.

10. The new SSISDB will be created and show in two places:
Database node
Integration Services node

11. Permissions:
Add user to SSIS_Admin role to be the admin for SSISDB

12. Configure Integration Services Catalog

13. SSIS Catalog SSISDB Folders-Organize the projects Projects
Catalog Properties
Log Properties
Project Versions
Folders-Organize the projects
Projects
Packages
Parameters
References
Environments
Variables
Permissions

14. Catalog properties:

15. Permissions You can manage permissions by using
Microsoft.SqlServer.Management.IntegrationServices namespace
SQL Server Management Studio UI
For a folder, use the Permissions page of the Folder Properties Dialog Box.
For a project, use the Permissions page in the Project Properties Dialog Box.
For an environment, use the Permissions page in the Environment Properties Dialog Box.
Transact-SQL (in SSISDB Database)
catalog.grant_permission
catalog.deny_permission
catalog.revoke_permission
catalog.effective_object_permissions: to view effective permissions for the current principal for all objects
catalog.explicit_object_permissions: to view permissions that have been explicitly assigned to the user.

17. Project Versions

18. Explore the SSISDB DB Objects
Let’s take look the SSISDB database

19. Project/Packages Related Tables
Those tables in Internal schema to store the SSIS project objects deployed to the IS catalog

20. Operation Tables
Those tables stored stat and log for the operation include: Deployment, execution, validation, etc..
Catalog.operations
Displays the details of all operations in the Integration Services catalog.

21. Integration Services Dashboard

22. Integration Services Dashboard

23. Other Standard Reports
All Connections Report
All Operations Report

24. All Validations Report: Summary of all Integration Services validations that have been performed

25. All Executions Report: Display the SSIS package executed in descending order.
Filter: Allow to select the Execution started from and to Date

26. View Messages

27. View Performance

28. Catalog Logging Levels
Description
None
Logging is turned off. Only the package execution status is logged.
Basic
All events are logged, except custom and diagnostic events. This is the default value.
Performance
Only performance statistics, and OnError and OnWarning events, are logged.
Verbose
All events are logged, including custom and diagnostic events.
An example of a diagnostic event, is the DiagnosticEx event. Whenever an Execute Package task executes a child package, it logs this event. The event message consists of the parameter values passed to child packages

29. Set for Server Side Default Level

30. Set for Individual Package
Right-click the package
Select Execute.
Select the Advanced tab
Under Logging level, select the logging level.

31. Performance level

32. Verbose level

34. Ways to Execute the SSIS Packages
SQL Job
DTExec /ISSERVER
Stored Procedure

35. SP to Execute SSIS Package
Catalog.Create_Execution
Creates an instance of execution in the Integration Services catalog.
This stored procedure uses the default server logging level.
Catalog.Set_Execution_Parameter_Value
Sets the value of a parameter for an instance of execution in the Integration Services catalog.
Catalog.Start_Execution
Starts an instance of execution in the Integration Services catalog.
Catalog.Stop_Operation
Stops a validation or instance of execution in the Integration Services catalog.

36. --CREATE Execution plan EXEC [SSISDB]. [catalog]
--CREATE Execution plan EXEC [SSISDB].[catalog].[create_execution] , OUTPUT, --Set Execution Parameters @parameter_name=N'LOGGING_LEVEL', @parameter_name=N'DUMP_ON_ERROR', --Start Execute the SSIS pCakge EXEC --Checking error = [Status] FROM [SSISDB].[catalog].[operations] WHERE operation_id AS AS Result = 4 =6 BEGIN RAISERROR ('SSIS Execution Failed: %s with return code %d', -- Message text. 16, -- Severity. 1,-- --1st --2nd parameter ); END
Status Code:
int
The status of the operation. The possible values are created (1), running (2), canceled (3), failed (4), pending (5), ended unexpectedly (6), succeeded (7), stopping (8), and completed (9).

37. SP for Validation Catalog.validate_project
Asynchronously validates a project in the Integration Services catalog.
Catalog.validate_package
Asynchronously validates a package in the Integration Services catalog.

38. Clean the Catalog Data

39. SQL Agent Job SSIS Server Operation Records Maintenance
EXEC [internal].[cleanup_server_retention_window]
SSIS Server Max Version Per Project Maintenance
EXEC [internal].[cleanup_server_project_version]
SQL Job created when you enable the IS catalog:
It contains two steps:
SSIS Server Operation Records Maintenance
EXEC SSISDB.[internal].[cleanup_server_retention_window]
SSIS Server Max Version Per Project Maintenance
EXEC [internal].[cleanup_server_project_version]

41. Create/Deploy Custom Report

42. Comparison SSMS Custom Reports RS Reports
No need to have SSRS installed
Need SSRS
Use current context; Execute in the context of Current Object Explorer
Stored in shared physical drives only
Stored in ReportServer.dbo.catalog
Parameter is invisible; Predefined Parameter to retrieve current object name & type
Support Report Parameters
Cannot be executed automatically
Could be executed programmatically
Not support subreports
Support subreports
Using the permission of current user; Read access to the physical report file location
Current user or delegated user

43. Adding customer report to SSMS
In Management Studio, right-click a node in Object Explorer
Point to Reports and click Custom Reports
In the Open File dialog box, locate the custom reports folder and select the XXXX.rdl file you want to add.
And then click Open.

44. Reference:
s/8966.getting-started-with-the-ssis-2012-catalog-and- dynamic-configurations-using-the-project-deployment- mode.aspx
us/library/bb aspx
us/library/bb aspx
us/library/bb aspx
integration-services.html

45. Thanks for your attending
Blog: