Books online state: “There is nothing a graph database can achieve, which cannot be achieved using a relational database.” Why then are we putting graph technology in SQL Server? To help me answer this question, I invite my friend AZ to chat about the Graph feature in SQL Server 2017 and introduce how graph differs from a relational model. If you have every tried to implement complicated hierarchies in SQL Server, you know what a pain this can be. I, for one, am hopeful this new feature will allow us to tackle the various relationships even though it may be lacking certain features compared with other graph databases.
Are you using graph technology in SQL Server or even another platform? I would be very interested to getting your thoughts on what you like and what you still find painful.
The show notes from today's episode can be found at http://sqldatapartners.com/2018/03/28/episode-129-graph-databases. Have fun on the SQL Trail.
To Devops or not to Devops, that is the question. We've talked before about how the developers have all the cool new tools, but this is slowly changing. For those in development or dare I say agile (gasp!) environments there is more need for automation, but getting there can be a real challenge. In this episode, we chat with John Morehouse about how he actually put into practice automated deployments for the database, some of his challenges, and how long it took to get there.
Are you trying to implement continuous delivery for the database? Let me know. I am very interested to hear your experiences.
The show notes from today's episode can be found at http://sqldatapartners.com/2018/03/21/episode-128-database-doing-devops. Have fun on the SQL Trail!
There has been a remarkable shift introduced in the new features of SQL Server--programming languages have been embedded into the database. This has led to a few "What are you thinking" questions from myself and others. It also opens new opportunities for those working with SQL Server and in this episode, I chat with Andy Roberts and Chris Hyde and discuss the new features of R and Python--why they are included, how data teams are changing, and what this means for the rest of us. As someone who does not and has not ever considered themselves a programmer, I don’t try to tackle any of the technical challenges of the language. We stay safe on the side of ideas, process, with a sprinkle of installation and setup.
One of the most compelling ideas from this conversation is the democratizing of data. Sure, this is not a new concept; however, now with a programming language in the database it will force a thinking realignment for those that traditionally called themselves gatekeepers. Where CLR couldn’t quite do the trick, I think the introduction of these languages is going to require increased collaboration with teams and force administrators to up their game as they tackle challenges of data distribution and data consumption.
I am interested to see what lies ahead and how consumers will use these new features. We already have some insights into R and while I won’t call it a smashing success—it is certainly useful to those who know how to take advantage of it and those numbers appear to be growing. With Python, I think we are increasing the breadth of those who can take advantage of analytics in the database, which I think only bodes well for those who enjoy working with SQL Server.
What about you? Is your team trying to implement R or Python? What new skills have you had to learn because of these changes? Hit me up on social media.
The show notes for today's episode can be found at http://sqldatapartners.com/2018/03/15/episode-127-developing-in-the-database. Have fun on the SQL Trail!
Have you attended a SQLSaturday? They are great events and in this episode we chat with a few organizers about what goes into putting on an event and what they think the future of these events looks like.
The show notes from today's episode can be found at http://sqldatapartners.com/2018/03/08/episode-126-sqlsaturday-edition. Have fun on the SQL Trail!