Machine Learning in the Database

  • Comments posted to this topic are about the item Machine Learning in the Database

  • I've been dealing with similar this week. The reality is, very few data sources for these reports allow for real-time execution of R code from the back-end outside of embedding R code on the front-end. From a small business standpoint, this is totally fine. But, when you get into larger organizations, having to manage hundreds of R code implementations on the front-end is a pain. Having the ability to store, execute, train, and return predictions from something as simply calling a stored procedure is extremely powerful. No other data source really does that in many of the front-end tools you may use to visualize the data.

    Thus, to force the machine learning down the path of writing all the code in the app versus storing it in the back-end is something you might want to think long and hard about. Simply storing the pre-trained data is not going to be enough if you get serious with ML.

  • You also have to ensure that the machine is learning what is actually necessary.  I recently bought a new Chevy Silverado and the amount of SPAM I now get about Chevy Silverado's being on sale is insane.  I just bought one... why the hell would anyone think I'm in the market for another?  Stupid.  Just plain stupid.  The machine learned how to be a total moroff ("Moroff" is worse than "Moron" because it's more off than on :D).

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Well, admittedly I'm old school here when it comes to this topic. I have to think that we would be smart to keep our servers focused on the traditional tasks of storage and retrieval of DATA for presentation to the front-end (either user machines or other servers) for them to analyze and create the INFORMATION for the end user.  While a single or a few analytical processes may be OK, unless there is really, really good design and development, it is very likely that there are going to be waits while data is manipulated taking cycles away from the data movement.  And unless we now get DBA's highly trained and experienced in the analysis process, our main focus is going to suffer.  As the old idea said, that I think originated years ago even before the client/server concept existed, use the KISS method - keep it simple, Stupid.  And of course, this harks back to earlier discussions regarding the continuing issue of how much detail data to retain online, how much summarization to do, etc.  Combining ever growing quantities of data with ever-increasing processing of that data appears to be a place we may not want to go.  When it comes to taking on all the processing tasks, it seems maybe we should 'be careful what we ask for - we just might get it'.

    Rick
    Disaster Recovery = Backup ( Backup ( Your Backup ) )

  • Jeff Moden - Tuesday, June 12, 2018 7:40 AM

    You also have to ensure that the machine is learning what is actually necessary.  I recently bought a new Chevy Silverado and the amount of SPAM I now get about Chevy Silverado's being on sale is insane.  I just bought one... why the hell would anyone think I'm in the market for another?  Stupid.  Just plain stupid.  The machine learned how to be a total moroff ("Moroff" is worse than "Moron" because it's more off than on :D).

    Exactly my point, Jeff.  DBA's are not likely to be in control of what all the code executing on their servers are doing, but it will be consuming resources that should be available for the storage and retrieval processes.  I'm for keeping all that workload off the servers.  Back when I started in mainframe days of the 60's we had no choice about it.  Anything that was to be done had to be in the same process.  Do we really want to go back to that?

    Rick
    Disaster Recovery = Backup ( Backup ( Your Backup ) )

  • skeleton567 - Tuesday, June 12, 2018 7:58 AM

    Jeff Moden - Tuesday, June 12, 2018 7:40 AM

    You also have to ensure that the machine is learning what is actually necessary.  I recently bought a new Chevy Silverado and the amount of SPAM I now get about Chevy Silverado's being on sale is insane.  I just bought one... why the hell would anyone think I'm in the market for another?  Stupid.  Just plain stupid.  The machine learned how to be a total moroff ("Moroff" is worse than "Moron" because it's more off than on :D).

    Exactly my point, Jeff.  DBA's are not likely to be in control of what all the code executing on their servers are doing, but it will be consuming resources that should be available for the storage and retrieval processes.  I'm for keeping all that workload off the servers.  Back when I started in mainframe days of the 60's we had no choice about it.  Anything that was to be done had to be in the same process.  Do we really want to go back to that?

    Agreed.  I'll also state that "BI" is frequently an oxymoron (although some good souls actually DO get it right!), machine learned or not. 😀

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Jeff Moden - Tuesday, June 12, 2018 7:40 AM

    You also have to ensure that the machine is learning what is actually necessary.  I recently bought a new Chevy Silverado and the amount of SPAM I now get about Chevy Silverado's being on sale is insane.  I just bought one... why the hell would anyone think I'm in the market for another?  Stupid.  Just plain stupid.  The machine learned how to be a total moroff ("Moroff" is worse than "Moron" because it's more off than on :D).

    How do you like the Silverado?  I bought a 2018 Chevy Colorado for the trip to/from Rhode Island.  I like the truck, handles well, and did well with the trailer we towed to Rhode Island.

  • Lynn, for what it's worth, I've been around trucks all my life and driven pickups since I was 16. (Now 75). I have a 2010 Ford F-150 with 110k miles, and it's the best I've ever had. We love it for long distance travel, choosing it over our Buick Park Avenue, for regular trips Indiana to Colorado, etc. Great comfort, ride, sound system, power enough to pull a 16' travel trailer, except for the highest mountain passes. We do those in our 4-seater ATV.??I

    Rick
    Disaster Recovery = Backup ( Backup ( Your Backup ) )

  • This was removed by the editor as SPAM

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

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