False. SSIS provides a Checkpoint capability which allows a package to restart at the point of failure.
Additional information: Checkpoints in SQL Server Integration Services (SSIS) Packages to restart from the point of failure
Question 2 - Can you explain what the Import\Export tool does and the basic steps in the wizard?
The Import\Export tool is accessible via BIDS or executing the dtswizard command.
The tool identifies a data source and a destination to move data either within 1 database, between instances or even from a database to a file (or vice versa).
Additional information:
SQL Server 2000 vs SQL Server 2005 Import and Export Wizard
Question 3 - What are the command line tools to execute SQL Server Integration Services packages?
DTSEXECUI - When this command line tool is run a user interface is loaded in order to configure each of the applicable parameters to execute an SSIS package.
DTEXEC - This is a pure command line tool where all of the needed switches must be passed into the command for successful execution of the SSIS package.
Additional information:
Execute a SQL Server 2000 DTS Package vs a SQL Server 2005 Integration Services Package
Question 4 - Can you explain the SQL Server Integration Services functionality in Management Studio?
You have the ability to do the following:
Question 5 - Can you name some of the core SSIS components in the Business Intelligence Development Studio you work with on a regular basis when building an SSIS package?
Question 6 - True or False: SSIS has a default means to log all records updated, deleted or inserted on a per table basis.
False, but a custom solution can be built to meet these needs.
Additional information: Custom Logging in SQL Server Integration Services Packages (SSIS)
Question 7 - What is a breakpoint in SSIS? How is it setup? How do you disable it?
A breakpoint is a stopping point in the code. The breakpoint can give the Developer\DBA an opportunity to review the status of the data, variables and the overall status of the SSIS package.
10 unique conditions exist for each breakpoint.
Breakpoints are setup in BIDS. In BIDS, navigate to the control flow interface. Right click on the object where you want to set the breakpoint and select the 'Edit Breakpoints...' option.
Additional information:
Breakpoints in SQL Server 2005 Integration Services
Question 8 - Can you name 5 or more of the native SSIS connection managers?
Additional information:
Connection Managers in SQL Server 2005 Integration Services
Question 9 - How do you eliminate quotes from being uploaded from a flat file to SQL Server?
In the SSIS package on the Flat File Connection Manager Editor, enter quotes into the Text qualifier field then preview the data to ensure the quotes are not included.
Additional information: How to strip out double quotes from an import file in SQL Server Integration Services
Question 10 - Can you name 5 or more of the main SSIS tool box widgets and their functionality?
Question 11 - Can you explain one approach to deploy an SSIS package?
One option is to build a deployment manifest file in BIDS, then copy the directory to the applicable SQL Server then work through the steps of the package installation wizard
A second option is using the dtutil utility to copy, paste, rename, delete an SSIS Package
A third option is to login to SQL Server Integration Services via SQL Server Management Studio then navigate to the 'Stored Packages' folder then right click on the one of the children folders or an SSIS package to access the 'Import Packages...' or 'Export Packages...'option.
A fourth option in BIDS is to navigate to File Save Copy of Package and complete the interface.
Additional information:
Deploying a SQL Server 2000 DTS Package vs. a SQL Server 2005 Integration Services Package (SSIS)
Import, Export, Copy and Delete Integration Services Packages in SQL Server 2005
Question 12 - Can you explain how to setup a checkpoint file in SSIS?
The following items need to be configured on the properties tab for SSIS package:
CheckpointFileName - Specify the full path to the Checkpoint file that the package uses to save the value of package variables and log completed tasks. Rather than using a hard-coded path as shown above, it's a good idea to use an expression that concatenates a path defined in a package variable and the package name.
CheckpointUsage - Determines if/how checkpoints are used. Choose from these options: Never (default), IfExists, or Always. Never indicates that you are not using Checkpoints. IfExists is the typical setting and implements the restart at the point of failure behavior. If a Checkpoint file is found it is used to restore package variable values and restart at the point of failure. If a Checkpoint file is not found the package starts execution with the first task. The Always choice raises an error if the Checkpoint file does not exist.
SaveCheckpoints - Choose from these options: True or False (default). You must select True to implement the Checkpoint behavior.
Additional information: Checkpoints in SQL Server Integration Services (SSIS) Packages to restart from the point of failure
Question 13 - Can you explain different options for dynamic configurations in SSIS?
Additional information: Using XML Package Configuration with SQL Server Integration Services (SSIS) Packages
Question 14 - How do you upgrade an SSIS Package?
Depending on the complexity of the package, one or two techniques are typically used:
Additional information:
Upgrade SQL Server DTS Packages to Integration Services Packages
Question 15 - Can you name five of the Perfmon counters for SSIS and the value they provide?
SQLServer:SSIS Service
SQLServer:SSIS Pipeline
BLOB bytes read - Total bytes read from binary large objects during the monitoring period.
Rows written - Total number of output rows in use by the data flow task at a point in time.
Additional information: Perfmon Counters for the Data Flow Engine in SQL Server Integration Services (SSIS)
No comments:
Post a Comment