or .. veni vidi viblogged
well, after a brief globe trotting to few places here and there, I had to go to where literally every other Indian IT employee goes. America. After spending most of my first 4 days here indoors I guess I am both qualified and bored enough to write this post. And after spending good amount of weekend time clicking remote or flicking matrimonials or licking your plate, I am sure you are also eager to read this post while trying to focus on work. So without further ….
My travel had nothing exciting to write home about, unless you want to call watching-6-movies – getting-served-by-male-air-hostesses – and-loosing-one-of-your-suitcases-in-transit exciting. Anyways what is really the matter with muscular and cold looking male air hostesses? Have I formed stereotypes watching too much of those red skirted kingfisher ladies or it is how they work in this part of the world? well .. whatever
So I walk out of the Columbus intl. airport feeling anorexic from all the in flight consumables and hail a cab. As I try to explain the driver where I wanted to go, I quickly learned that he knows nothing except driving. I mean not even reading or writing. I guess this is what us consultants call verticalization. So while I spell letter by letter and point it on the GPS unit our man was able to configure the address and get the directions. He is a sweet man though.
The first cultural shock came in a matter of 23 seconds. I have quickly learned that I have reached US on a super extra long weekend called thanksgiving weekend. Well, I couldn’t be more thankful though. I was in no mood to work after what seemed like a zillion hours of listening to “stow your brain in the overhead compartment, buckle your belt to the seat and restore your feet from the seat in front of you”. So I spent rest of my day wondering what my wife has packed in the other suitcase that went missing in the transit. I realized it contained important life saving stuff like my camera, bathing soap, bed sheet, pillow and eatables.
Next morning my room-mate suggested that we go get some milk from the near by pharmacy. So we walked across the street and entered in to a place that looked almost like half the size of Chennai central railway station. You could buy Christmas trees, digital cameras, bedsheets apart from medicines there. I must tell you this, here everything that is in liquid form (can be liquified) is measured in gallons, including but not limited to espresso shots, coke or tequila.
Rest of my 4 days here involved more of walking across the street to buy some coffee or wearing too many clothes and watching some Simpson’s while sitting on the couch. I guess that part matches pretty much with the life in India, except that I still miss my suitcase.
A last tip to anyone curious enough to read till here: a gallon actually means 3.7 ltrs but feels like a whole lot of coffee that an entire state of Goa can drink in a morning.
PS: Image belongs to http://www.commercialrealtygroup.com
One Response to “SQL vs. Power Query – The Ultimate Comparison”
Enjoyed your SQL / Power Query podcast (A LOT). I've used SQL a little longer than Chandoo. Power Query not so much.
Today I still use SQL & VBA for my "go to" applications. While I don't pull billions of rows, I do pull millions. I agree with Chandoo about Power Query (PQ) lack of performance. I've tried to benchmark PQ to SQL and I find that a well written SQL will work much faster. Like mentioned in the podcast, my similar conclusion is that SQL is doing the filtering on the server while PQ is pulling data into the local computer and then filtering the data. I've heard about PQ query folding but I still prefer SQL.
My typical excel application will use SQL to pull data from an Enterprise DB. I load data into Structured Tables and/or Excel Power Pivot (especially if there's lot of data).
I like to have a Control Worksheet to enter parameters, display error messages and have user buttons to execute VBA. I use VBA to build/edit parameters used in the SQL. Sometimes I use parameter-based SQL. Sometimes I create a custom SQL String in a hidden worksheet that I then pull into VBA code (these may build a string of comma separated values that's used with a SQL include). Another SQL trick I like to do is tag my data with a YY-MM, YY-QTR, or YY-Week field constructed form a Transaction Date.
In an application, I like to create a dashboard(s) that may contain hyperlinks that allow the end-user to drill into data. Sometimes the hyperlink will point to worksheet and sometimes to a supporting workbook. In some cases, I use a double click VBA Macro that will pull additional data and direct the user to a supplemental worksheet or pivot table.
In recent years I like Dynamic Formulas & Lambda Functions. I find this preferable to pivot tales and slicers. I like to use a Lambda in conjunction with a cube formula to pull data from a power pivot data model. I.E. a Lambda using a cube formula to aggregate Accounting Data by a general ledger account and financial period. Rather than present info in a power pivot table, you can use this combination to easily build financial reports in a format that's familiar to Accounting Professionals.
One thing that PQ does very well is consolidating data from separate files. In the old days this was always a pain.
I've found that using SQL can be very trying (even for someone with experience). It's largely an iterative process. Start simple then use Xlookup (old days Match/Index). Once you get the relationships correct you can then use SQL joins to construct a well behaved SQL statement.
Most professional enterprise systems offer a schema that's very valuable for constructing SQL statements. For any given enterprise system there's often a community of users that will share SQL. I.E. MS Great Plains was a great source (but I haven't used them in years).
Hope this long reply has value - keep up the good work.