Alternative when using Excel in reporting

Even using modern technologies and available database tools (even free alternatives) are available today, it seems that a huge number of users are still very convenient to use Excel IN ALLYING! Therefore, since the database developer works as one of these users, I have to let them use Excel simply because it is very convenient for them to use it. Especially for seniors who never seemed to let Excel go and accept the new tool. Currently, to make their experience as smooth as possible and at the same time automated, I use a lot of database queries inside Excel, whether it be browsing, SQL or stored procedures. Mostly on ad-hoc (but then became permanent) reports. My question is, is there any hope of improving this situation? I am sure that many organizations use the same method. Is it possible to completely replace this scheme with something more logical and effective both in data collection and in reliability? I am thinking about using Sharepoint. Am I on the right track?

+4
source share
3 answers

I also struggled with this problem in the past and I can say that what worked for me was two-way.

Step 1 - Make a Good Alternative

It seems that you have already done this, depending on the system there will always be some random report that someone should run in accordance with their “Business Need”. There is no way that you can squeeze all this into your system as it would fill out reports and users would become blind.

Step 2 - User Training

Show them a new way to create your own reports (SSRS Business Objects) and make sure they are convenient for them. This is the hardest part, as some people like their comfortable blanket and do not want to leave it. Give them some templates and some standard reports, maybe even a couple will develop one or two reports on their table with them so that they can get comfortable.

I will leave a little daily WTF, once this expert business manager was an expert in business objects. She did reports on the left and center, but she treated her like a gigantic version of excel, and her work was littered with examples of this, i.e. One report she wrote was to get year-end totals. No problem, I hear you cry, just do

SELECT SUM(DealAmount) where DealDate Between X and Y 

No, not our business expert, the mood here is superb, it was too much like black magic, so she made it so that she could go back to EVERY ONE CASE done this year, and then combined it on the client side to give her a common . In step I and the users wow, having reduced this report to 104 MB, it took 17 minutes to run a report up to 100 kb, which ran for about 15 seconds.

+1
source

I would go the other way around. And I mean this, without making queries and database connections in Excel, but using some kind of web application so that users (through the wizard) generate the data they need and export it to Excel for work.

Thus, you will have the following benefits:

  • Excel files do not have DB connections (and probably passwords).
  • There is no problem distributing Excel files with new queries, views, etc.
  • Centralized approach to data retrieval
  • Excel for users using it
+1
source

That day I liked using Crystal Reports for special reports. I am not sure about the current state, as it seems that SAP purchased the product: http://www.sap.com/solutions/sapbusinessobjects/sap-crystal-solutions/index.epx

+1
source

Source: https://habr.com/ru/post/1315336/


All Articles