Welcome to Salvo(z)

SSIS logging is configured on a package-by-package basis.  SSIS provides a flexible event logging environment that allows developers to configure: the container or scope to log (generally the entire package), the type of events to log, and the log provider type (SQL Server, Windows Event Log, Text Files, SQL Server Profiler or XML Files).

I discovered some undesirable behavior with the SSIS  Excel Data Source.  Although this issue has been well-documented for a while, I thought it is worth mentioning again.

A few months back I purchased the book “Expert Cube Development with Microsoft SQL Server 2008 Analysis Services” by Chris Webb, Alberto Ferrari and Marco Russo.  I recently finished reading this book and thought I’d share my impressions.

Tonight I was greeted with an obscure exception being thrown from the Visual Studio designer when I tried to open a DevExpress report. The application and report worked fine when it was compiled and executed. The stack trace given by Visual Studio designer was not very helpful upon first (and second, and third) glance. A few choice lines from the stack trace (pasting the the complete stack trace would be a bit of an overkill):

The SSIS dataflow script component is useful for complex data cleansing and data validation.  I recently used the dataflow script component to validate the format of emails and phone numbers based on a regular expression.