Does one need DB/SQL knowledge to write reports?

[pietb]

Coming from a programming/db background I have experienced the nuances of query building. Currently, our operations department has the task of writing reports. They report on themselves and the rest of the company. The people in charge of writing reports have the functional knowledge of the business, which I think is useful, but not the database or SQL knowledge. So, my questions are:

1. Does someone need knowledge of databases and SQL to be a report writer even if they are given drag and drop reporting software like Crystal Reports?

2. Is it safe to have a department report on themselves?

I am writing a proposal to suggest:

1. That reporting be its own department
2. Have an experienced report writer
3. Have a business analyst mediate between the entity requesting the report and the report writer

...but I would like concrete data to backup my proposal. If you have supporting or contradicting ideas to my thoughts I would like to hear them.

Also, can anyone point me to any documentation/articles that back up your answers?

Thanks in advance.

 

[blom0344]

I have no backup from documentation, just about 10 years experience with BO.

Here's my 2 cents:

I'd say yes and no

The whole point of having advanced reporting tools is - for a mayor part - shielding the reporter from the SQL generated. So ,if you are going for the most straightforward reports you will never want to know what goes on beneath.
If you want to squeeze everything out of BO (and there is a lot to be had) you may benefit from a working knowledge of the SQL generated, the database addressed and the universe in between.
In my experience it does pay off, when those who create reports have some idea what is involved in the backend.
They will no have to reproduce the SQL from scratch, but some idea of what is smart and what is not will not hurt.

Contrary to what vendors claim there is a level beyond merely drag and drop and you are well of with some technic al insight..

You did not state what business you work in, but that may be a important factor. Working in the retail business there is no way I could work with properly devised requests reaching my desk. The immediacy of requests forces me to create a quick example and use enduser input to mould it into it's final form. If you work with really formal design procedures you could take the time to formalize the request first.

I bet Steve will have a firm view on this as well



Ties Blom
Information analyst

 

[xlbo]

Just wanted to back this view up - it is very depedant on what you want to achieve - I started out as a basic report writer with no knowledge of SQL and managed to create several suites of reports. After 6 years of working with BOBJ, I am now pretty proficient in SQL and can use a lot of the deeper recesses of BOBJ -

does this make my reports any better ? not necessarily. Does this mean I have more possibilities when writing reports ? Certainly

I would always be wary of people reporting on themselves but as long as any assumptions / criteria are always stated with the data, there is not that much they can do....

I would say that a Business Analyst is probably unnecessary as if you are going along a "Report Writer" route, a decent report writer should be able to interact with users to obtain requirements..

Rgds, Geoff

We could learn a lot from crayons. Some are sharp, some are pretty and some are dull. Some have weird names and all are different colours but they all live in the same box.

Please read FAQ222-2244 before you ask a question