Fix performance, connectivity, execution, and failed logic issues by using the debugger in SSIS

-
Checking your execution results progress tab
When you are testing your packages, and troubleshooting issues, the details of the execution results can be found in the last tab of the package design environment. A point of possible confusion can be how SSIS changes the name of this one tab depending on if the package is executing or the package execution has been stopped. The last tab is labeled as follows:

Execution Results tab When the package is not executing you can see the results of the last run.
Progress tab When a package execution is in-progress you can see the real-time execution results. Once the package execution has been stopped, you can still see these results under the Execution Results tab.

Package execution reports in Management Studio
Once you have a package executing successfully, you want to monitor and track its progress. SQL Server Management Studio (SSMS) provides a very detailed, color-coded package execution report. This report can be accessed directly from within Management Studio:















This brings up the All Executions reports, which displays the package execution statistics number on top: Failed, Running, Succeeded. Below the overall statistics is a table with all of the details about each time a package was executed.







The Status column shows if the package Succeeded, Failed, or was Terminated for some reason. The next three columns contain hyperlinks that take you to specific reports. The level of detail you see in this report strongly depends on your logging level. So if you don’t see any information, or too much information, adjust your logging level. You can export the report results by right-clicking anywhere in the report.

Here is the information contained in each of the hyperlinks:
  • Overview
    • Details about the execution: execution result, environment used, overall duration, who started the package, parameters, and values
    • The duration and result, master and child packages information
  • All Messages
    • Displays warnings and error messages of the package executions
    • If Diagnostic logging is enabled, you may get pages and pages of details
  • Execution Performance
    • The breakdown of package performance
    • It shows individual package executions duration, along with a three-month average and standard deviation

Comments

Post a Comment

Popular Posts

Non-blocking, semi-blocking, and blocking transforms in SSIS

-
Not all Data Flow transforms are created equal. In fact, some are much faster and require a  lot less memory (non-blocking transforms). Others are slower while consuming much more  memory (blocking transforms), and some are in between (semi-blocking transforms). We don’t  always have a choice if we need to use a certain transform to do a certain specified task, but  it is good to know the differences between these types of transforms so that we can better  understand performance and resource utilization issues. Synchronous and asynchronous There is another related aspect about Data Flow transforms, which is their ability to quickly  process a row as they are coming into the transform, independently of any other rows that  came before or after (synchronous transforms). The other type of transform needs to be  dependent on some or all of the rows that come before and after (asynchronous transforms). On the whole, non-blocking transforms are also synchronous, thus are fast and
Read more

Implement additive, semi-additive, and non-additive measures

-
Additive Additive measures are numeric values that can be summed up by all the dimensions in the  fact table, for example the Sales Amount. These are the most common measures and they are  the easiest to understand and implement. Semi-additive Semi-additive measures are numeric values that can be summed up by some dimensions  in the fact table, but not all. In most cases, they can be aggregated by any other dimension  except time.  An example of a semi-additive measure is Account Balance. You can determine  the ending balance of an account at the end of a month, but adding up these monthly account  balances do not make sense. Semi-additive measures are usually found in fact tables that store  periodic snapshots of data. Non-additive Non-additive measures, as the name implies, are measures that cannot be summed up.  These measures include percentages such as Discount Percent, ratios such as Profit Margin, and  averages such as Average Unit Cost. Exam 70-767
Read more

Design an appropriate storage solution, including hardware, disk, and file layout

-
Image
The data warehouse storage’s performance can be measured by  analyzing the time it takes for read and write operations to complete, known as latency , and by  analyzing how much data volume it can read or write in each time frame, known as throughput .  High latency and low throughput can be an indication of an improper selection for the  storage infrastructure or incorrect hardware and software configurations. Performance of a storage subsystem can  be estimated based on several criteria: Volume of data Rate of change and growth of the data Data retention policy Number of concurrent users Typical workloads expected Two important metrics associated with storage are throughput and Input/Output Per  Second (IOPS) . Throughput is a measure of the amount of data that can be transferred in a  period. This is typically measured in megabytes or gigabytes per second. IOPS is the number of  I/O read or write operations that can complete in a second.  It is important
Read more