RTVS builds on Visual Studio, which means you get numerous features for free: from using multiple languages to word-class Editing and Debugging to over 7,000 extensions for every need:
A polyglot IDE – VS supports R, Python, C++, C#, Node.js, SQL, etc. projects simultaneously.
Editor – complete editing experience for R scripts and functions, including detachable/tabbed windows, syntax highlighting, and much more.
IntelliSense – (aka auto-completion) available in both the editor and the Interactive R window.
R Interactive Window – work with the R console directly from within Visual Studio.
History window – view, search, select previous commands and send to the Interactive window.
Variable Explorer – drill into your R data structures and examine their values.
Plotting – see all of your R plots in a Visual Studio tool window.
Debugging – breakpoints, stepping, watch windows, call stacks and more.
R Markdown – R Markdown/knitr support with export to Word and HTML.
Git – source code control via Git and GitHub.
Extensions – over 7,000 Extensions covering a wide spectrum from Data to Languages to Productivity.
Help – use ? and ?? to view R documentation within Visual Studio.
I’ve been using it for a little while and it’s pretty snazzy for integrating with SQL Server R Services. R Studio is still more feature-rich, but RTVS is definitely catching up.
I recently got back from Strata West 2017 (where I ran a very well received workshop on
Spark). One thing that really stood out for me at the exhibition hall was
datashaderfrom Continuum Analytics.
I had the privilege of having Peter Wang himself demonstrate
datashaderfor me and answer a few of my questions.
I am so excited about
datashadercapabilities I literally will not wait for the functionality to be exposed in
rbokeh. I am going to leave my usual
rmarkdownworld and dust off
Jupyter Notebookjust to use
datashaderplotting. This is worth trying, even for diehard
For the moment, it looks like datashader is only available for Python, but it’s coming to R.
I am proud to announce that we contributed to the latest revision of the Microsoft SQL Server on VMware best practices guide, freely available at this address. This document outlines some of the common VM-level tweaks and adjustments that are made when running enterprise SQL Server VMs on VMware platforms. This guide is considered a must-read if you manage these sorts of SQL Servers, which cannot be treated as general purpose virtual machines.
This guide was recently updated for vSphere 6.5, and we consider it an absolute must for your enterprise management library!
If you manage SQL Server instances on VMware, it’s definitely worth the read.
So, can you run DBCC CHECKDB on a read only database? Should you run DBCC CHECKDB on a read only database?
tl;dr: YES AND YES!
Many forms of corruption that I’ve seen have come from storage. Sure, there have been bugs that were to blame, but yeah. Most of the time, it’s the storage going all yucky.
Erik also explains some gotchas, so read the whole thing.
The question: “Why does it say ‘Consume live data sources with full interactivity’ as one feature while the other feature says ‘Access on-premise data using the Data Connectivity Gateways’, while it is obvious that if you need to connect to an on-premise data source to consume live data it has to be through a gateway?”
Okay, this is how I would explain this:
Read on for the explanation.
A few episodes ago, I talked about how learning about Write Ahead Logging was a light bulb moment for me, and helped me learn tons of concepts about backups and recovery. This week, we talk about when SQL Server turns things upside down and doesn’t use write ahead logging: and what it has to do for recovery in these special cases.
Click through for the video.