DCSIMG
How to not add another table to your DB (by using Excel!) - Ella Maschiach's BI Blog

Ella Maschiach's BI Blog

BI, Olap Technologies, Tools, System Analysis and Design

News

About Ella Maschiach

Business Inteligence

How to not add another table to your DB (by using Excel!)

Hey blog, how are you? I know I haven't been here for quite some time now... I guess I needed a break. Some time for myself. And I know you were waiting here for me all that time. Being patient and understanding. Knowing that one day, I'll come back. Thank you. I missed you. I think this time, I'm here to stay.

So, the topic for today is how to not work automatically and adding a table to your database. About a year ago, I created a report in SSRS for a user of mine on the distribution of workers of the municipality in different cities in Israel. A year had passed and she needed the same report, but this time she needed to group the cities by areas. My first instinct was to ask her to give me an Excel file containing the cities and the areas they belong to. I was about to import that data to a table I would create for that in my DB. Boris, our trusted DBA, gave me another suggestion. Instead of adding a table and keeping it updated for a query that's usually run just once a year (for the yearly report), he suggested I keep it all in Excel.
That means, I get an Excel file mapping the cities to the areas, download my own Reporting Services report to the same Excel workbook and then use a Vlookup to map the areas to the cities. Last but not least, I created a pivot table on the new data with the total of workers per area and per city. 

Needless to say, it didn't take me a lot of time. My customer was delighted to get such a quick response (and I was happy to be done with it so quickly :)). She was eager to know how I managed it so quickly and was interested in learning it herself (as before she planned on doing all the mapping of cities to areas by hand). I told her it wouldn't be a problem to teach her how to do the same herself.

Excel is a powerful and popular tool and Vlookup is a strong function within it - use it in your work and it'll benefit both your work and your customer's! 

Comments

Miky Schreiber said:

Hi Ella,

It's great you're blogging again.

The solution you written about is great for this specific user, but the solution is only good for her. If another user will want to use the city-to-aeras table for any reason, he won't have it because it's stored in an end-user computer. That is why sometimes it's better to store that kind of knowledge in a centralized place.

Miky.

# May 15, 2011 12:29 AM

Ella Maschiach said:

Hey Miky,

First of all, I completely agree with you. Using excel is appropriate because of the setup of the situation – it’s a report that’s run just about once a year by one user. That’s not the case with most reports.  I guess a sort of workaround might have been to put the Excel in a SharePoint portal in an area shared by a few users. Though most of the times – I do just add the table.

Thank you for your important feedback!

It’s good to be back :)

Ella

# May 15, 2011 11:12 AM
Leave a Comment

(required) 

(required) 

(optional)

(required) 


Enter the numbers above: