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.
Today, Docker or Kubernetes are obvious choices. But, back in 2015, these technologies were just emerging and hoping for massive adoption. How do tech companies make the right open source technology choices early?
Visualize project management metrics from Harvest like hours tracked, billable hours, billable amount, non-billable hours, expenses (and more) in minutes.
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.
One question that I’m often asked is ‘how do I justify funding for a BI project?’ The answer I give is that to win funding you need to stop thinking about BI as a project.
Here is how Charles Drengberg built a simple client communication hub in WordPress that allows clients to check the status of their marketing at any time.
