January 16, 2006 at 3:20 am
Hi,
I would like to see a thread dedicated to conceptual issues in SQL 2005.
For example, I am trying to use SQL server to abstract our data gathering tasks and relational model away from the user.
So, I build my data sources in SSIS, and create a load of tables in the local server.
I now have the tables created, and each one is related to an item of interest in our manufacturing environment. For example we have machines, products and sales.
And now the reporting model itself. What? All the help files have obviously been written by tecchies in a hurry - they are not even remotely related to what the report model actually does, and frankly all it tells you about are the default values. What does it do? Does anyone know? Surely Microsoft knew what they were trying to achieve when they built it? What happened to the guy who designed it? Did he leave? Why can't he write the helpfile?
Anyway, its doing my nut. Any ideas?
Thanks
Rich
January 19, 2006 at 8:00 am
This was removed by the editor as SPAM
January 20, 2006 at 3:25 am
Actually I've found some things out and now I feel a bit conned....
The report model DOES NOT allow you to abstract your data model to a set of business relationships understandable to the user - it merely allows you to present this abstraction, you have to do all the legwork yourself - this is where I was coming unstuck.
Not very impressive - I'm still asking myself what I've done with 2005 that I couldn't have done in 2000 - alright it gives me a framework to stitch all these things together, but this framework is so complex I can't see much mileage in it....
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply