Nah, no topic.

Here's a link to a pretty sweet application[^] that Nick told me about tonight at the IADNUG meeting. It allows you to covert VB.Net code to C# and vice versa, on the fly, on the web. Not only can you upload files, but you can type your code as well, and it will parse it as you type. Yes my friends, you heard me correct... You no longer have to click a “Convert” button to have your code converted!!! On a serious note, the app is sweet, and is getting bookmarked for those days I really don't want to think about a minor syntax difference between the two languages.

Found a new tool today: nSurvey[^] Looks to be pretty useful, and is open source. It's not the most intuitive application in the world, however, it has a nice feature base once you figure it out. It don't think it be long before Community Server swallows it. But that's another story.

Mike Benkovich[^] presented tonight at the IADNUG[^] meeting. It went pretty well. After just coming from the SQL Summit in Minneapolis, I wasn't very interested in the topic, but he did make some great points about Analysis Services in SQL 2005. Mike will also be presenting here in Des Moines in early June. I'm looking forward to his next presentation.

On that note, of my 2 readers, who actually uses OLAP in a production application? I totally agree that OLAP can be very useful in many different situations. However, it seems to me that those situations tend to be large databases that hold massive amounts of transactional data, where running snapshot type reports could take a long time. I have been recently presented with a question of using OLAP for a relatively small set of data that gets updated infrequently. My opinion is that this situation best lends itself to writing procs or using the object model to retrieve data. Reporting Services would then be used to display the data. What are your thoughts?

Heh... I think I just found the topic for my next post. “Is a viewstate of 221KB to large?” Looks like I've got some investigation to do.