Often times a date range is used in a where clause with a start date and an end date that are the same. The dates however are entered with the intention of getting that single day worth of data. By default T-SQL will look at that but not give you the full 24 hours worth... Continue reading →

Do not put too many parent-child dimensions in a cube. This tip is magnified when the dimension contains custom rollups or unary operators. Yes, some of you might say, “but they are so powerful!” Well with power comes responsibility! In this case the responsibility is to safe guard against poorly performing queries. So keep in... Continue reading →

So it really isn’t news, but VS.NET 2008 is really coming from what I can tell. I’m stoked about this, I’m really looking forward to doing Silverlight work too. I think I’ll probably even hack together a solution in VS 2005. I’ve seen a few entries out there recently which I could pull on to... Continue reading →

So I got to thinking, and after searching around a bit, I didn’t find much, “A blog post is in order!” So here is what I was researching. Where and when is it a good idea to start breaking out to multiple cubes? What is the best practice about splitting up cubes or segmenting data... Continue reading →

When you’re developing attributes that have a bunch of members, let’s say more than a million (1,000,000,000), you should definitely use numeric keys. Don’t use strings or anything like that or you will suffer delays. With business intelligence cube development we’re talking about airport length delays here! So next time you’re tearing through some ETL... Continue reading →