Question 2
You install a SQL Server 2012 database engine instance on a production server. A month later, you install SQL Server 2012 Integration Services (SSIS).
You must develop an SSIS project and deploy it to the server by using the Project Deployment model.
Operations Log records that are outside the configured retention period must be cleaned automatically.
You need to create the SSIS catalog on the production server and ensure that the operations log cleaning requirement is met.
What should you do? (Each correct answer presents part of the solution. Choose all that apply.)
Start the SQL Server Browser service.
Enable Cross Database Ownership Chaining
Start the SQL Server Agent service
Enable Ad Hoc Remote Queries.
Correct answer: BF
Explanation:
B: To create the SSISDB catalog in SQL Server Management StudioOpen SQL Server Management Studio. Connect to the SQL Server Database Engine. In Object Explorer, expand the server node, right-click the Integration Services Catalogs node, and then click Create Catalog. Click Enable CLR Integration. The catalog uses CLR stored procedures. Etc. F: SSIS projects, packages, parameters, environments, and operational history are all stored in the SSISDB database so if you have hundreds of SSIS packages or packages that run every few minutes you could see how the database storing all the historical information would grow exponentially.Also included when you enable this feature is a SQL Server Agent Job called SSIS Server Maintenance job: References: http://msdn.microsoft.com/en-us/library/gg471509(v=sql.110).aspxhttps://www.mssqltips.com/sqlservertip/3307/managing-the-size-of-the-sql-server-ssis-catalog-database/
B: To create the SSISDB catalog in SQL Server Management Studio
Open SQL Server Management Studio.
Connect to the SQL Server Database Engine.
In Object Explorer, expand the server node, right-click the Integration Services Catalogs node, and then click Create Catalog.
Click Enable CLR Integration.
The catalog uses CLR stored procedures.
Etc.
F: SSIS projects, packages, parameters, environments, and operational history are all stored in the SSISDB database so if you have hundreds of SSIS packages or packages that run every few minutes you could see how the database storing all the historical information would grow exponentially.
Also included when you enable this feature is a SQL Server Agent Job called SSIS Server Maintenance job:
References:
http://msdn.microsoft.com/en-us/library/gg471509(v=sql.110).aspx
https://www.mssqltips.com/sqlservertip/3307/managing-the-size-of-the-sql-server-ssis-catalog-database/