Tải bản đầy đủ - 0 (trang)
15-16. Creating an SSIS Catalog

15-16. Creating an SSIS Catalog

Tải bản đầy đủ - 0trang

Chapter 15 ■ Logging and Auditing



7.



Expand Configuration Properties in the left-hand pane and click Deployment. Add

the server to which you will be deploying the project and the Server Project Path. The

dialog box should look like Figure 15-9.



Figure 15-9.  SSIS project properties for deployment

8.



Click OK to finish configuring the project properties.



9.



Deploy your SSIS package by right-clicking project in the Solution Explorer and

choose Deploy.



10.



Click Next if you see the start page.



11.



In the Select Source pane, confirm that the project is the one that you wish to deploy.

The dialog box should look like Figure 15-10.



897

www.it-ebooks.info



Chapter 15 ■ Logging and Auditing



Figure 15-10.  Selecting the source project to deploy to an SSIS catalog

12.



Click Next.



13.



In the Select Destination pane enter or browse for the server and path to which you

wish to deploy the project. The dialog box should look like Figure 15-11.



898

www.it-ebooks.info



Chapter 15 ■ Logging and Auditing



Figure 15-11.  Selecting the source project to deploy to an SSIS catalog

14.



Click Next. The dialog box should look like Figure 15-12.



899

www.it-ebooks.info



Chapter 15 ■ Logging and Auditing



Figure 15-12.  The project deployment review pane

15.



Click Deploy. The results pane of the Deployment wizard will appear once the project

has been deployed. It will be similar to Figure 15-13.



900

www.it-ebooks.info



Chapter 15 ■ Logging and Auditing



Figure 15-13.  The results pane following the successful deployment of an SSIS project

16.



Click Close.



How It Works

In essence, the SSIS catalog is an SQL Server database that allows you to store SSIS projects. Once a project is

deployed into this database—or Catalog as it is called—you can run packages from a centralized location. You

can also request different levels of logging for events and counters without making any modifications to the

packages that have been deployed to the catalog.



901

www.it-ebooks.info



Chapter 15 ■ Logging and Auditing



The process that we used consists of the following four steps:





Create the SSISDB database that SQLServer uses to manage SSIS projects.







Create any folder(s) into which you want to deploy your project.







Prepare the project.







Deploy the project.



It is, quite simply, as easy as that. You can then see any projects that you have deployed by expanding the

Integration Services Catalogs folder for the server to which you deployed the project. You will see the folder

that you created, the project, and all the packages in the project—something like the completely trivial example

shown in Figure 15-14.



Figure 15-14.  The Integration Services Catalog in SSMS



Hints, Tips, and Traps





The SSIS catalog database is called SSISDB and this name cannot be changed.







When redeploying a project, you get an alert warning you that you are about to overwrite

an existing project.







You can run any packed stored in the catalog by right-clicking it in SSMS and selecting

Execute . . . followed by OK.







CLR Integration must be enabled for an SSIS catalog to be created. If this is not the case in

your environment, the following is the T-SQL snippet to enable it:

sp_configure 'show advanced options', 1;

GO

RECONFIGURE;

GO

sp_configure 'clr enabled', 1;

GO

RECONFIGURE;

GO



902

www.it-ebooks.info



Chapter 15 ■ Logging and Auditing



15-17. Reading Logged Events and Counters from the SSIS

Catalog

Problem

You want to look quickly at the events and counters made available in the SSIS catalog using SQL Server 2012.



Solution

Display the prebuilt reports made available from SSMS. Here is how:

1.



Expand Integration Services Catalogs ➤ SSISDB ➤ ➤ Projects ➤

➤ Packages.



2.



Right-click the package to execute and choose Execute.



3.



Select the Advanced pane and set the logging level to Performance.



4.



Click OK. The package will run. The following dialog box will appear as in Figure 15-15.



Figure 15-15.  Opening an Overview report in SSMS

5.



Click Yes to show Overview report. You will see something like Figure 15-16.



903

www.it-ebooks.info



Chapter 15 ■ Logging and auditing



Figure 15-16. The Overview report in SSMS

6.



You can refresh a report while the underlying package is still running. Indeed, you

should always ensure that a package has finished before using any data provided by

the catalog reports.



How It Works

Now that you have deployed a project to the SSIS catalog, you can view events and metrics every time that you

run a package. Indeed, this option is available by default when you use SSMS to run a package from the catalog.

The following are the three basic reports that are available:





The Overview report







The Performance report







The Messages report



You can switch from one to another by clicking the hyperlinks in each report. You can also see the execution

details for each task in a package by clicking the Execution Path elements in the Overview report. In Figure 15-16,

these are \Test and \Test\CarSalesDataFlow.

The SSIS catalog lets you choose a logging level; however, it must be chosen before executing a package. The

four available levels are shown in Table 15-9.



 T

Note table 15-9 is taken with permission from Matt Masson’s blog entry at

www.mattmasson.com/index.php/2011/12/what-events-are-included-in-the-ssis-catalog-log-levels/.



Matt is coauthor of SQL Server 2012 Integration Services Design Patterns (apress, 2012).



904

www.it-ebooks.info



Tài liệu bạn tìm kiếm đã sẵn sàng tải về

15-16. Creating an SSIS Catalog

Tải bản đầy đủ ngay(0 tr)

×