When developing an SSIS package, sometimes it can be frustrating trying to troubleshoot various issues and faults with the package. And if you're not a seasoned SSIS developer, you may not be sure about the best way to solve your problem. Thankfully, Microsoft has seen fit to bless us with some useful tools for troubleshooting. Control Flow Troubleshooting When working in the Control Flow, there are several useful ways to troubleshoot during the development of your SSIS Package: 1) Use breakpoin...
Read More
I recently developed a series of reports that allows the user to view recently failed jobs by querying the MSDB database for job history information. By clicking the link "Click here to re-run the job", users can attempt to re-run the failed job right from reporting services. To see a detailed explanation on how to accomplish this, check out Devin Knight's blog here . And if you click the link "View job history and error messages", you can see the history of failures of the selected job and view...
Yesterday I was doing some work with the system tables in SQL Server 2008, specifically the tables related to jobs and job execution history. Those tables store dates and times in seperate fields as integer values, which is horrible for reporting. To remedy this, I put together a simple little function that I can pass the intDate and intTime values to and have it spit out a single datetime value. This way I don't have to write all the TSQL every time I want to convert the date and time into a si...
A common reporting requirement an end user may request is the ability to exclude certain records from a report using a parameter. For example, I've had end users request the ability to hide records where a certain field is 0 or NULL. In this example, I'll be using the Adventure Works database and adding the functionality to hide records where the Previous Year's Sales = 0. There's a couple ways to do this. One way would be to doing all the work in the TSQL. Here is the TSQL I began with: SELECT ...