If you have an Azure account (possibly through your MSDN subscription) here is the easiest way to get up and running with SQL Server 2016.
First go to the Azure Portal – http://portal.azure.com
Search and find the SQL Server 2016 CTP3 in the Data and Analytics Marketplace in Azure.
Create the Virtual Machine.
Start the Virtual Machine once it is created and then once it is running Connect with RDP.
Once it is started up you can search and add items to Start as well as Taskbar such as SQL Server Management Studio, SQL Server Configuration Manager, SQL Server Reporting Services Configuration Manager, etc.
Turn off the IE Enhanced Security for Administrators.
Download and install the latest version of SSDT for SQL Server – http://msdn.microsoft.com/en-us/library/mt204009.aspx
SSDT for Visual Studio 2015 for SQL Server 2016 now includes the database projects as well as the BI project templates, so you no longer need to download and install two separate installs. If you already have Visual Studio 2015 installed then a smaller download (install) will be used to add in the additional template projects.
The installer will download and then install the components. This will take approximately 10 to 15 minutes on the Virtual Machine.
Then add SQL Server Data Tools 2015 to the Start and/or Taskbar for easy access.
Review the SQL Server Components installed.
Based on this as well as reviewing the summary setup log located here – C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\ – we can see that the Database Engine was installed along with Data Quality Services, Analysis Services (multidimensional), Reporting Services (Native), Integration Services, Management Tools, and Master Data Services.
We still need to install Analysis Services (Tabular), Advanced Analytics Extensions, and also complete the configuration of Reporting Services.
So to complete the install components we will access the setup in the following location – C:\SQLServer_13.0_Full\. First we will install the Advanced Analytics Extensions. This is part of the process so that we can use SQL Server R Services.
Additional steps are required to complete and start using the Advanced Analytics Extensions in SQL Server.
Use the link provided in the Warning to access the complete steps to getting R services completed on the server so that you can start utilizing R code with SQL Server.
Rule Check Result
Rule "Post-installation steps are required for Advanced Analytics Extensions" generated a warning.
The feature Advanced Analytics Extensions requires some post-installation steps after completing SQL Server setup. Please follow the steps outlined in the link http://go.microsoft.com/fwlink/?LinkId=626645 (Ctrl-C to copy)
This installation for the extensions will also install the SQL Server Launchpad.
Next we will run the installer again and get an Analysis Services Tabular instance installed. For this we will need to install a named instance since multidimensional SSAS was used for the default.
Once that is done then run the Reporting Services Configuration Manager to complete the SSRS Native setup.
Once connected go to the Web Services URL and click Apply button. Then go to the Database page and use the Change Database option to create a new report server database. Next go to the Report Manager URL and click Apply.
Other items that you might want to do are setup Execution Account, backup Encryption Keys, setup Subscription Settings for file share access, and lastly Power BI Integration!
We will setup the Power BI integration so that we can use the new Pin to Power BI capabilities when we create our Reporting Services reports so that we can pin and share content in our Power BI dashboards!
The last item that we have to do is go to Report Manager and we can install the new Report Builder.
You will see that Report Builder has a new theme as well as the new Chart Types – Treemap and Sunburst which are great for displaying hierarchical data.
There you go, up and running and ready to explore some of the new SQL Server 2016 CTP3 capabilities.
More resources on new features in SQL Server 2016 CTP3: