Re: Data mining tools

Kevin Powick wrote:
Jeff Swanberg wrote:

Hi Jeff,

1 - Given my example, do you have an opinion on the direction to go
(graphical query builder vs. cube)?

That's a bit hard for me to say. If you want to slice, dice, and
drill down large amounts of aggregate data, then an OLAP cube is a
good way to go. However, having re-read your original post, a query
builder might be best.

I actually worked with high school management systems for a number of
years, so I think I know where you are coming from. We were often asked to create reports as you describe. Ex: List the children with attendance below 85% that are living in single parent households and have one or more siblings also attending the school.

While that report example _might_ be useful, it was incredible the number of, IMO, completely silly reports we were asked to create.

My standard procedure is to not allow the users to create their own
reports. They don't know the db structure, and will never bother learning it. As far as they are concerned, I'm the analyst, so I should be the one slicing and dicing data, not them. Anything complex, and all rare reports, I'll do as a once-off. For reports that are used often, I let them enter certain parameters using date edits, radio groups, and check boxes, then construct the SQL on the fly. They prefer this method - giving them fewer choices is better, because it limits their ability to screw it up.



--
Jon Purvis
Wildlife Technical Programs Lead
Texas Parks and Wildlife Department
Austin, TX
.