On April 19, 2017 Microsoft held an on-line conference Microsoft Data Amp to showcase how Microsoft’s latest innovations put data, analytics and artificial intelligence at the heart of business transformation. The keynotes speakers were Scott “Red Shirt” Guthrie who is an Microsoft Executive Vice President (fairly high on the food-chain), and Joseph Sirosh a Corporate Vice President, head of the Information Management and Machine Learning group. Joseph probably knows a thing or two about data, and Scott - well, Scott knows A LOT!
During the keynotes, Scott and Joseph shared how Microsoft’s latest innovations put data, analytics and artificial intelligence at the heart of business transformation. A big enabler for this is SQL Server 2017 (the “artist” formerly known as SQL Server V.Next), which introduces a lot of very cool new “stuff”.
The keynote speeches were followed by recorded short:ish sessions drilling down into certain aspects of Microsoft’s new offerings. If you are interested in the various presentations at Microsoft Data Amp, they all are on Channel 9.
What caught my eye was the announcement of how SQL Server 2017 now supports Python as an extensible script engine. When Microsoft introduced support for R in SQL Server 2016, rumors immediately surfaced how other engines also would be supported, where Python was high on the list (Julia another one).
The rest of this post is a brief introduction to executing Python code in SQL Server 2017, in essence I just want to be able to execute some sort of Python code.
The installation steps of external scripts engines doe not differ much (at all) from the installation in SQL Server 2016, apart from the fact you now can install Python. So if you feel you need more information abut the install process, please go and read my Microsoft SQL Server 2016 R Services Installation post.
I downloaded the SQL Server 2017 CTP 2.0, and after battling trying to register (I assume a couple of other people had the same idea as myself), I managed to get an
iso down to my machine and installed it as an instance. During Feature Selection at installation time we can see that the promise of Python was not a lie. It is part of Machine Learning Services, as in Figure 1:
Figure 1: Python Option In Database
Looking further we also see how Python can be installed as a stand-alone engine:
Figure 2: Python Option In Database
The stand-alone installation option is useful, for example,if a data scientist want to run Python (or R) on his or her own machine.
NOTE: You may wonder why, in Figure 2, the check boxes for R as well as Python is checked, but “dimmed” out? This is because, on this particular machine, I have already installed the standalone versions once.
OK, so after successful installation, and if you have installed the SQL Server engine, R services and Python services you should see something like so in the
Figure 3: Finished Install
Now, let’s test this “shiny new thing out”. Oh, in this post I leave out all “grunge” about the launchpad service, etc. If you are interested go ahead and read about it in the previously mentioned post.
Execute Python Code in SQL Server 2017
After we have done the installation, but before we can execute the Python (or R) code we need to enable the execution of external scripts. As I covered in the post Microsoft SQL Server 2016 R Services Installation you enable external scripts by changing the configuration as in Code Snippet 2 AND restarting the instance.
Code Snippet 2: Execute sp_configure
After having enabled everything let’s execute
sp_execute_external_script. The code is very, very basic - more or less the least what we can get by with for Python. It does have some similarities with the code in the Microsoft SQL Server 2016 R Services Installation post, and Code Snippet 2 shows the code:
Code Snippet 3: Test That Python Installation Works
In Code Snippet 3, we say that the language is Python (the
@language parameter), and that the script we want to execute is a Python print statement:
print("The Answer Is 42!!!"). That’s all!
When executing this, something like so should be printed out in the Messages tab in SQL Server Management Studio:
Figure 4: Result from Python Execution
We have now executed our first Python code in SQL Server 2017. Just for “giggles”, let us ensure that we still can execute R code:
Code Snippet 4: Test That Execution of R Still Works
That should work, and you will see something like so:
Figure 5: Result of Execution of R Script
That seemed to work OK, let’s ship it!
We have in this post seen how SQL Server 2017 introduces support for execution of Python in addition to R scripts. There is obviously a lot more to the above than what I have covered in the above, and I will definitely come back to both Python as well as R in future posts.
If you have comments, questions etc., please comment on this post or ping me.
comments powered by Disqus