Find something in SQL Server, whether in Integration Services or elsewhere that just doesn't operate the way you think it should? Have you combed the 'net for answers, including the MSDN forums, Books Online, and plain old Google just to find out that "that's the way it is"?
What do you do next? Let the people who can do something about it know - the SQL Server dev team. How, you ask? Through Microsoft Connect. Connect is the feedback and bug-reporting portal for many Microsoft products.
There have been multiple very valuable bug submissions and suggestions made via this site - but it's very underpublicized IMO, so a suggestion that appears there tends to look like a "niche" request rather than something truly desired by the user community. I highly recommend that you sign up for Connect, the SQL Server section in particular, and review the feedback. Here are some of my favorites (odd that most of them are started by me...):
"Managed" Raw Files
Extend Raw File Metadata to include Sort Order
SSIS detects end of data flow components in the wrong way
Add Cardinality Indicator in Analysis Services Dimension Attribute Relationship Designer
ADO NET Source component does not recognize schema changes
Add user defined function support to the SSIS expression language
Add new context menu item to Sql Server Management Studio
Click through on any of those, log in with your LiveID, and rate the feedback. Add your own comments, workarounds, or validations. Browse through the "most recent" feedback (bugs and suggestions) from this page (which is notoriously hard to locate) and see if any of the items jump off the page at you.
Update (Nov 16, 2008): Douglas Laudenschlager (of the MS SSIS Team) confirms that Connect is the best way to make your opinion on bugs in SQL Server known in his blog post Your vote on Microsoft Connect influenced SQL Server 2008 Service Pack 1
No comments:
Post a Comment