The Purpose of a Database

  • Comments posted to this topic are about the item The Purpose of a Database

  • Technology aside, when a database project is conceptualized, the organization should ask itself whether it is truly providing value for our customers... or just hoarding data. I'm thinking about internet service or web content providers who capture and warehouse detailed usage data or demographics data about their customers. I'm particularly calling bull$hit on organizations who claim that sharing this data with 3rd parties provides value for their customers.

    "Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

  • Eric M Russell - Sunday, January 22, 2017 7:52 AM

    I'm particularly calling bull$hit on organizations who claim that sharing this data with 3rd parties provides value for their customers.

    It can provide value for the shareholders :Whistling:

    Gaz

    -- Stop your grinnin' and drop your linen...they're everywhere!!!

  • Steve Jones - SSC Editor - Saturday, January 21, 2017 12:59 PM

    A great quote from a blog on machine learning in SQL Server: "...nobody buys a DBMS for the sake of DBMS. People buy it for what it enables you to do". The post is from Rimma Nehme, who has given a few keynotes at the PASS Summit. While the focus of the post is how you can implement deep neural network learning with R Services in SQL Server, I thought that quote stands out for any database, relational or NoSQL, from Microsoft, another vendor, or open source...

    Nothing is there but for the benefit of the company be it software, hardware, people, offices or paperclips.

    Gaz

    -- Stop your grinnin' and drop your linen...they're everywhere!!!

  • Steve Jones - SSC Editor - Saturday, January 21, 2017 12:59 PM

    ...we need to ensure we are providing value for our customers.

    Whether it is value they recognise or not e.g. auditing, security, validation, etc.

    Gaz

    -- Stop your grinnin' and drop your linen...they're everywhere!!!

  • Eric M Russell - Sunday, January 22, 2017 7:52 AM

    Technology aside, when a database project is conceptualized, the organization should ask itself whether it is truly providing value for our customers... or just hoarding data. I'm thinking about internet service or web content providers who capture and warehouse detailed usage data or demographics data about their customers. I'm particularly calling bull$hit on organizations who claim that sharing this data with 3rd parties provides value for their customers.

    Tend to agree. When I was out of work three years ago I registered with some agencies. Shortly after I started suffering "information shared with our partners" syndrome. The result is your CV ends up with some other agency and you then get e-mails about job vacancies from them. The problem is that every time you get rid of one you get stuff from another. Three years later I am still getting all sorts of rubbish mainly now for jobs that I have no suitable experience or qualifications for! Likewise Amazon and EBay are forever sending suggestions that I neither want nor need!

    Back to the original topic. A database is often described as an organised collection of data. This is the case with the main project I am involved in. Previously information was mainly held in user defined directories (where they often forgot what was meant by "fred" three months down the line. This was supplemented by hand written notes and human memory (quite fallible). Now you can easily find out basic information on a person (name, address, DOB, etc.) together with previous and current results (and notes). This both prevents errors and saves a vast amount of time.

  • It's not just value for our customers, but the value we add to the organization. One of the top questions our IT directors ask, "How will this save us time, money and resources too?" Does this reduce the amount of people hours we spend doing something through some other business process? Will this improve performance to cut down on machine hours? Etc

    I do agree it's silly to argue about how we go about that either through SQL Server, NoSQL or something someone custom made. Doesn't matter as long as value is there.

  • Eric M Russell - Sunday, January 22, 2017 7:52 AM

    Technology aside, when a database project is conceptualized, the organization should ask itself whether it is truly providing value for our customers... or just hoarding data. I'm thinking about internet service or web content providers who capture and warehouse detailed usage data or demographics data about their customers. I'm particularly calling bull$hit on organizations who claim that sharing this data with 3rd parties provides value for their customers.

    There's a whole new avenue growing up with license plate readers. There is some legitimate value (looking for stolen cars, wanted individuals) but as soon as a plate is determined to be 'clean' it should immediately be deleted. This is often NOT done by authorities, and a legal fight may be developing.
    Additionally these are being purchased by private marketing concerns and installed on parking areas etc. These organizations then are selling the user visitation histories to marketing and other parties.

    ...

    -- FORTRAN manual for Xerox Computers --

  • xsevensinzx - Monday, January 23, 2017 6:24 AM

    It's not just value for our customers, but the value we add to the organization. One of the top questions our IT directors ask, "How will this save us time, money and resources too?" Does this reduce the amount of people hours we spend doing something through some other business process? Will this improve performance to cut down on machine hours? Etc

    I do agree it's silly to argue about how we go about that either through SQL Server, NoSQL or something someone custom made. Doesn't matter as long as value is there.

    Agreed,  The "golden hammer" argument tends to lead to silliness like forcing EVERYTHING into an RDBMS, even if the questions you answer from the data in question don't need or don't care about the internal relationships. If there really isn't any desire or need to peel the onion a little deeper, then holding on to that internal structure is ultimately wasteful, so perhaps time to move that particular data to a document database or something more economical.

    ----------------------------------------------------------------------------------
    Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?

  • xsevensinzx - Monday, January 23, 2017 6:24 AM

    It's not just value for our customers, but the value we add to the organization. One of the top questions our IT directors ask, "How will this save us time, money and resources too?" Does this reduce the amount of people hours we spend doing something through some other business process? Will this improve performance to cut down on machine hours? Etc

    I do agree it's silly to argue about how we go about that either through SQL Server, NoSQL or something someone custom made. Doesn't matter as long as value is there.

    Google already does that with cell phone location data.

    "Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply