SSIS Attunity Connectors

Recently I had to create an SSIS package that transferred a huge amount of data between an Oracle database and a MS SQL Server database. I began creating an SSIS package that used an existing linked server connection that the client had already been using to perform similar data transfers. To my dismay, the performance of the linked server was dismal. Instead of using the linked server I decided to go with the OOTB OLE DB data source available in SSIS. This increased my performance dramatically. However, when I spoke to a colleague at TCSC, he recommended that I try the Microsoft Connectors for Oracle by Attunity. I had never heard of these connectors, but I was intrigued, so I downloaded them and ran some performance test.

The following tests results we recorded while debugging through Visual Studio, so real numbers will be better than what I have recorded, but the results do represent without a doubt the performance differences between the different connections.

	Attunity	OLE DB	Linked Server
3000 rows	2 seconds	6 seconds	10 seconds
10,000 rows	3 seconds	10 seconds	20 seconds
100,000 rows	19 seconds	1 minute 28 seconds	3 minutes 2 seconds
500,000 rows	1 minute 23 seconds	7 minutes 35 seconds	16 minutes 18 seconds
1,000,000 rows	2 minutes 38 seconds	16 minutes 37 seconds	30 minutes 28 seconds

Upgrade your version of WSPBuilder for a more traditional development experience

In many ways a seasoned ASP.Net developer can have a difficult time learning SharePoint 2007 development because they have become accustomed to the practices ascribed to by the Microsoft ASP.Net team. One of these practices is so benign and intuitive, that most developers find it incomprehensible that it is not available when using a WSPBuilder project template. The practice that I am referring to is right clicking your declarative markup and selecting “View Code”. The menu item is not available, because the WSPBuilder Project type is based on the standard C# project type, and does not include the web application project type. Because of this, you cannot add regular web application based items such as web forms and web controls. This has lead many developers, including myself, to develop SharePoint solutions by hand, manually linking our declarative markup and code behind files, all the while not using designers and in some cases intellisense.

Visual Studio Styles

I was recently asked where I got the Visual Studio color scheme that I used in this post:
http://www.viamacchina.com/2011/06/a-better-inputformsection-for-sharepoint.html

Originally I had been turned on to the VS Theming trend by Scott Hanselman’s post about theming Visual Studio.

http://www.hanselman.com/blog/VisualStudioProgrammerThemesGallery.aspx

When I went back to his blog to get the link for his post, I saw that it has been updated and now there is an entire site dedicated to Visual Studio themes:

http://studiostyl.es/

There are a ton of great themes on this site, and you can even make your own.

For the most part theming your environment is just a fun way to beak up the monotony of an application that you spend WAY too much time with. But, I have also found that after switching to a darker theme that I have reduced the amount of eye strain and fatigue associated with marathon coding sessions.

Have fun!

A better InputFormSection for SharePoint

One of my biggest annoyances with developing solutions SharePoint 2007 is the fact that many of the web controls available in the SharePoint framework do not support the same development paradigm that traditional ASP.Net controls support. Specifically, many controls in the Microsoft.SharePoint.WebControls namespace do not support two way data binding. The best example of this is the InputFormSection control. Like many ASP.Net Templated controls, the InputFormSection control allows you to encapsulate items of your choosing in regions within the control. The control takes care of the layout and positioning of your controls, and reduces the need for redundant declarative markup.

GhostDoc - My favorite “New to Me” extension for Visual Studio

Commenting our code is a necessary but sometimes painful exercise for developers. We tend to scrutinize our object structure, method names, and overall terseness and readability of the code itself, but leave commenting for last. I recently ran across a free extension for Visual Studio that makes adding XML documentation comments for your code as simple as a key stroke.