November 2009 - Posts
Last weekend I spend some time installing Visual Studio 2010 beta 2 and Team Foundation Server 2010 beta2. I now have a nice server with 12 Gb of RAM so I have some space to run virtual environments side-by-side. :-)
Installation went smoothly but configuration of TFS single server failed with the following error:
“TF255040: Install SQL Server Reporting Services or at a minimum SQL Client Connectivity Tools on the application tier to ensure Analysis Services object model is present for warehouse processing.”
So I started the SQL Server 2008 setup and thought I fixed the error by installing Reporting Services and SQL client tools, but the error remained. The good news about such a specific error code is that you can use it in your search query and so did I.
I found the solution in this MSDN forum.
The solution was easy, just restart the TFS configuration tool:
“The problem in beta2 is we scan for those assemblies once and don't re-scan so after you install to SQL client tools, you need to close and restart the wizards.”
Clear error code, easy solved. Let’s move on!
Last week the Professional Developers Conference (PDC) was held in the USA. At this conference Microsoft gives an insight in the future of their products and ambitions.
Also news about BizTalk was presented. At least 2 new releases were announced:
BizTalk Server 2009 R2, with these features:
- Visual Studio 2010 support
- SQL Server 2008 R2 support
- Windows Server 2008 R2 support
- Enhanced designer tool for mappings
- FTPS adapter
- Performance tuning dashboard (to allow easy access to the BizTalk performance (latency) knobs)
- Improved support for event processing (used for RFID)
- Powershell scripts to automate management
- New System Center Operations Manager pack
BizTalk Server vNext, with this focus:
- Deep application platform alignment, including AppFabric (aka Dublin) and WF 4
- Enterprise connectivity for AppFabric
- On-premises Server and Cloud Service Symmetry
A video about the roadmap can be viewed here.
Want to know more about these exiting announcements, take a look here:
At the moment I’m on a project which involves SQL Server Integration Services 2008. I had experience with DTS packages back in SQL Server 2000, but things have changed quite a bit.
After some reading and trying I built a new package. It was quite easy, reading data from one table, adding a column and writing it to another table. I used the Ole DB data flow source and because the destination was a SQL Server I decided to use the SQL Server destination data flow.
After a few runs I found out that the data in my destination table was malformed. Some fields contained correct data, but most were wrong. It looked like the data was shifted in one way or another.
Adding debugging to the package showed me that the problem had to be in the SQL Server destination data flow.
Some trial and error work didn’t result in a solution so I finally replaced the SQL Server destination data flow with the Ole DB destination data flow. It turned out to do the trick!
I’m not sure why SSIS behaved like this, because the data entering the data flow component was ok.