• jtc900502 (9/14/2012)


    Thanks for the reply Craig.

    Currently the users are not accessing the SPs. They have tried to pull data into excel (MS Query) using the physical tables but had a hard time using the same joins used in the report or could not replicate the complex calculations, so they thought if they have access to the report data set it would make their lives easier and all they have to do is join them to other report data sets.

    Out of curiousity, why not let them export the report(s) to excel directly and then do whatever they needed to with them, instead of fighting to create tables repeatedly that you'll be constantly changing on them mid-usage?

    I could just let them use the SPs in excel (MS Query) but then they wont be able to join it with any other data set. I think that might be a limitation of Excel or MS Query.

    I think I'm starting to see your difficulty. You're trying to allow non-designers design level access to the results so they can ad-hoc themselves into infinity.

    Um, ow.

    I think you might be approaching this the wrong way, but I'm not sure if I've even understood the problem in its complete difficulty. However, it sounds like your users are trying to do some serious BI work. My first question for that is why do they need real time data for BI work, that's pattern analysis that happens over weeks or months, not the last 15 minutes. If they're constantly just trying to pull up a particular pattern of recent data for business needs, well, build the reports for 'em and then look to another solution for the BI work.

    My guess is you've got a twizzler of a problem where you've just got too many strands of different issues all wrapped up together. Split 'em out. Some users will have immediate data needs. Look those over, figure out THAT best solution, which will probably be you building a few more reports and some tweaks to get them 'just right'.

    Next, look to SSAS for your BI analysis. Once a cube is built some rudimentary training can get the marketing and business guys to be able to manipulate and look into their pattern data out of real-time with more historical stuff. A little practice at that and they can describe to you the cube they actually WANTED instead of the one they got originally.

    Mind you, I'm guessing and inferring a LOT here as to the problems and what you're hoping for the end result beyond what you've described to me. There might be value in simply backing up the database and leaving it available to everyone to restore to a local install of SQL Express on their own machines and letting 'em loose on it. I would not however, under any circumstances, allow direct table access to non-developers in a real-time upkeep environment. You're begging for a disaster and a few thousand migraines.


    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]

    Twitter: @AnyWayDBA