Feedback on Working with Multiple Database Platforms

Featured Article(s)
Troubleshooting SQL Server 2008 Bulk Copy Problems
In this article, Alexander Chigrik explains some problems that you can have when you work with SQL Server 2008 bulk copy. He also tells how you can resolve these problems.

Featured Scripts
UDF – Calc distance
This UDF calculates the distance between two locations by passing in the latitude and longitude of each location…. (read more)

Feedback on Working with Multiple Database Platforms
(Sorry about the issue yesterday with the editorial; here it is, today – SW)
Several people wrote in with thoughts on using a different database for different portions of your applications (yikes!) in hopes of optimizing it. Here’s what different people had to say…

David writes "Actually you are spot on. If you can’t write code that can function on a single platform you have [no] right to expect me to keep your turd running. The support issues are unbelievable. We have one of these we are currently trying to replace because no one, even the author, can figure out where the problems in it are. We are pretty sure no recovery is even possible. The business manager has told our IT staff to get rid of it, whatever it takes."

Jeff wrote in with his perspective – "Not only would the issues you pointed out (trouble-shooting, recovery, etc.) become an even more complex (and possibly error prone) process, imagine what the DEVELOPMENT would be like? Do you need different architects to design the different pieces now, due to “specialized knowledge”? How about distinct DBA-type resources? Will you development tool-of-choice interface natively with all the storage platforms? While I understand that, in theory, you can optimize every part to the Nth degree, I think the reality of developing and deploying such an application would be horrific."

…and Pam wrote "I agree that using multiple database engines is overkill (choose one: Oracle/Sybase/SQL Server …), but not all data belongs in a database. Images, large documents that are considered “living” (always changing), and other things of this kind. Use the right tool to do the job, but put the links in the database."

This final item is an important point. perhaps not using multiple databases, but the other side of this is indeed true. Use the best tool for the job in terms of what you actually put in the database. There are definitely cases where elements don’t need to be stored in the database. Images and the like are great examples of things to possibly reconsider in terms of where they’re stored.

TechEd Experiencing a Bit of a Rebirth
Interesting watching what’s happening at TechEd this week. There is a huge push on cloud-based services and items, from an IT-perspective and from an end-user perspective. Where TechEd has for years been focused on product roadmaps, on addressing security, performance, compliance and the utility of the platforms, this year it’s all about a responsive cloud component and integration, along with the end-user experience associated with self-service business intelligence.

While I don’t think this is a bad thing, it is certainly a change. It’s really amazing to see the information flow change to address the changes in our environments that Microsoft is projecting and supporting. The tools are really quite cool and the integration from a security standpoint, from an IT-perspective and from an end-user perspective is very compelling. We can’t wait to dig deeper into the mix and see how things play out.