Skip to content

shannonlowder.com

Menu
  • About
  • Biml Interrogator Demo
  • Latest Posts
Menu

Business Intelligence Concepts

Posted on March 28, 2008April 12, 2011 by slowder

The phrase business intelligence is pretty old, 1958. In the early 90’s the term came to refer to the “concepts and methods to improve business decision making by using fact based systems.” So business intelligence is the means for taking all of the data in your organization and pull out the relationships. By finding these relationships you can make smarter decisions about how to manage your organization.

Currently there are two goals for modern Business Intelligence

  1. put as many facts as possible in front of decision makers
  2. put as many facts in front of everyone

Let’s say you worked in a tele-sales department. You have a fixed number (at least in the short term) of sales makers. You have a fixed number of leads (in the short term). The more efficient you are at converting a call to a sale, the more money you make. What do you do to maximize your profits.

  • Identify your strongest and weakest sales people — If you know how effective they are you can either eliminate the weaker candidates, or use the stronger candidates to mentor the weaker ones.
  • Maximize the amount of time your sales people are talking to people, and minimize the amount of time they are waiting for a call to be made. — Most of us have caller ID now, and if we don’t recognize the number, we screen it first. Therefore if you call a number and it never picks up, when do you give up on calling that number?
  • Identify your easy sales — Are some people more prone to spur of the moment purchases? Of course some are. What if you could find those people who buy time and time and time again?

There are many more relationships you could start looking for, but these I’ve actually done some research on and found a positively correlating dataset. It should show you what types of relationships you’re trying to discover, based on a certain business model.

In order for Business Intelligence (BI) to work you have to have rapid access to a lot of data. Typically your databases are set up to record transactions. Combining data from every transaction can extremely time consuming. BI addresses this issue through data warehousing. A Data Warehouse is a very large database set to optimize data reads.

A data mart is just a mini data warehouse that contains the portion of the whole data base that relates to specific division or group within your company.

The down side to your data warehouse? The amount of time it takes to transform your transactional data into your data warehouse. Also, the amount of data you may need to keep on hand to show a trend could require you to hold on to many terabytes of data… This could become costly.

The good news is hard drive space is always the cheapest component in a server build (per unit). It’s time that you can never seem to buy. Over the coming months, I’ll introduce you to some tools and techniques for using BI in your own company. You’ll see SSAS and SSRS, as well as new and interesting ways of using SSIS to pull over data for analysis.

As always, if you have any questions, please send them in. I’m here to help you learn as much as you can about Microsoft SQL!

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • A New File Interrogator
  • Using Generative AI in Data Engineering
  • Getting started with Microsoft Fabric
  • Docker-based Spark
  • Network Infrastructure Updates

Recent Comments

  1. slowder on Data Engineering for Databricks
  2. Alex Ott on Data Engineering for Databricks

Archives

  • July 2023
  • June 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • October 2018
  • August 2018
  • May 2018
  • February 2018
  • January 2018
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • June 2017
  • March 2017
  • February 2014
  • January 2014
  • December 2013
  • November 2013
  • October 2013
  • August 2013
  • July 2013
  • June 2013
  • February 2013
  • January 2013
  • August 2012
  • June 2012
  • May 2012
  • April 2012
  • March 2012
  • February 2012
  • January 2012
  • December 2011
  • November 2011
  • October 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • May 2011
  • April 2011
  • March 2011
  • February 2011
  • January 2011
  • December 2010
  • November 2010
  • October 2010
  • September 2010
  • August 2010
  • July 2010
  • June 2010
  • May 2010
  • April 2010
  • March 2010
  • January 2010
  • December 2009
  • November 2009
  • October 2009
  • September 2009
  • August 2009
  • July 2009
  • June 2009
  • May 2009
  • April 2009
  • March 2009
  • February 2009
  • January 2009
  • December 2008
  • November 2008
  • October 2008
  • September 2008
  • August 2008
  • July 2008
  • June 2008
  • May 2008
  • April 2008
  • March 2008
  • February 2008
  • January 2008
  • November 2007
  • October 2007
  • September 2007
  • August 2007
  • July 2007
  • June 2007
  • May 2007
  • April 2007
  • March 2007
  • February 2007
  • January 2007
  • December 2006
  • November 2006
  • October 2006
  • September 2006
  • August 2006
  • July 2006
  • June 2006
  • May 2006
  • April 2006
  • March 2006
  • February 2006
  • January 2006
  • December 2005
  • November 2005
  • October 2005
  • September 2005
  • August 2005
  • July 2005
  • June 2005
  • May 2005
  • April 2005
  • March 2005
  • February 2005
  • January 2005
  • November 2004
  • September 2004
  • August 2004
  • July 2004
  • April 2004
  • March 2004
  • June 2002

Categories

  • Career Development
  • Data Engineering
  • Data Science
  • Infrastructure
  • Microsoft SQL
  • Modern Data Estate
  • Personal
  • Random Technology
  • uncategorized
© 2025 shannonlowder.com | Powered by Minimalist Blog WordPress Theme