Systems | Development | Analytics | API | Testing

Analytics

How to transfer BigQuery tables between locations with Cloud Composer

BigQuery is a fast, highly scalable, cost-effective, and fully-managed enterprise data warehouse for analytics at any scale. As BigQuery has grown in popularity, one question that often arises is how to copy tables across locations in an efficient and scalable manner. BigQuery has some limitations for data management, one being that the destination dataset must reside in the same location as the source dataset that contains the table being copied.

Delivering Customised Workspaces with Enhanced BI to the Finance Sector

Continuing my series of blogs examining the products, services and client benefits borne out of Yellowfin’s partnerships, I’m pleased to introduce our new fintech partner, ChartIQ. ChartIQ provides HTML5 components and the Finsemble integration platform to banks, brokerages, trading platforms, and financial portals worldwide.

3rd-Generation Business Intelligence (Part I)

I’m seated here on the balcony of our rented apartment in Chamonix looking up at Mont Blanc. It’s an incredible view but its beauty is deceiving and as anyone who has climbed knows, all too often the summit is not the one you can see. In the case of Mont Blanc, the perspective is such that the Dôme du Goûter seen in the foreground often looks bigger. I can assure you it’s not.

BigQuery and surrogate keys: a practical approach

When working with tables in data warehouse environments, it is fairly common to come across a situation in which you need to generate surrogate keys. A surrogate key is a system-generated identifier that uniquely identifies a record within a table. Why do we need to use surrogate keys? Quite simply: contrary to natural keys, they persist over time (i.e. they are not tied to any business meaning) and they allow for unlimited values.

Are you missing out leaving important data standing on the outside?

Every now and then you can't beat a bit of Meat Loaf, the singer not the food, as I've not had the pleasure to taste it. I recently found myself recalling a cult classic "Standing on the outside" not because of any failed break up but thinking about the abundance of data available externally that can be used in combination with your internal data. Unfortunately, many are still leaving this data standing on the outside.