SSIS: Design Warnings

Aug 31, 2012 at 6:51 AM

Great feature guys, love the concept and totally agree with all the warnings implemented to date.  Here are my ideas for further warnings:

- OLE DB Destination with a connection to SQL Server but not in "Fast Load" mode
- OLE DB Source or Lookup with a connection to SQL Server where SELECT is not prefixed with SET ANSI_WARNINGS OFF;
- Union All Transformation with unmapped Input columns
- IsolationLevel and TransactionOption checks - e.g. highlight where property value for Package varies from the child containers and/or objects, or where any property varies from a preference (e.g. ReadUncommitted / Supported)
- No Log Provider defined
- Naming Standard checks e.g. Data Flow Task name must start with DFT
- Execute the Design Warnings at the Project level, and iterate through all the packages in the Project.
- Show an Info message if the check completes without detecting any warnings

Coordinator
Aug 31, 2012 at 6:06 PM

Great suggestions. I added these to the work item for these best practice warnings:
http://bidshelper.codeplex.com/workitem/23649

Incidentally, I thought you could Ctrl-Click to select multiple packages then launch Design Warnings to scan multiple packages. But I was wrong. That's only on other SSIS features in BIDS Helper. Thanks for reporting.