Download SQL Server Data Tools (SSDT) | Microsoft Docs

Table of Contents
Download SSDT
Changelog for SSDT
Data-Tier Application Framework - License Terms
Previous releases of SSDT and SSDT-BI
SQL Server Tools
License Terms - SSDT
Download SQL Server Data Tools (SSDT)
4/26/2017 • 3 min to read • Edit Online
SQL Server Data Tools is a modern development tool that you can download for free to build SQL Server
relational databases, Azure SQL databases, Integration Services packages, Analysis Services data models, and
Reporting Services reports. With SSDT, you can design and deploy any SQL Server content type with the same ease
as you would develop an application in Visual Studio. This release supports SQL Server 2017 through SQL Server
2005, and provides the design environment for adding features that are new in SQL Server 2016.
Download SQL Server Data Tools 17.0 for Visual Studio 2015
Download Data-Tier Application Framework (DacFx) 17.0
SQL Server Data Tools
Version Information
The release number: 17.0
The build number for this release: 14.0.61704.140
What's New
Support for SQL Server 2017 for database projects, IS projects and BI projects
Support for Azure Analysis Services
Ignore column order in database projects
PowerQuery integration and support for 1400 level models
IS package support ofr Microsoft Dynamics AX and CRM online through OData
Complete list of changes available in the changelog
To use SQL Server Data Tools in Visual Studio 2017 see this section below
Available Languages
This release of SSDT can be installed in the following languages:
Chinese (People's Republic of China) | Chinese (Taiwan) | English (United States) | French
German | Italian | Japanese | Korean | Portuguese (Brazil) | Russian | Spanish
ISO Images
An ISO image of SSDT can be used as an alternative way to install SSDT or to set up an Administrative Installation
point. The ISO is a self-contained file that contains all of the components needed by SSDT and it can be
downloaded using a restartable download manager, useful for situations with limited or less reliable network
bandwidth. Once downloaded, the ISO can be mounted as a drive or burned to a DVD.
Chinese (People's Republic of China) | Chinese (Taiwan) | English (United States) | French
German | Italian | Japanese | Korean | Portuguese (Brazil) | Russian | Spanish
Download Visual Studio
Download Visual Studio Community 2015
Installing SSDT without Visual Studio pre-installed
If you don't have Visual Studio installed on your machine, installing SSDT for Visual Studio 2015 will also install a
minimal “Integrated Shell” version of Visual Studio 2015. This version of Visual Studio is free to install and use on
as many machines as you wish. It gives you all the SQL Server project types, plus SQL Server Object Explorer and
other SQL tools experiences.
If you do have Visual Studio 2015 Community Edition (or above) installed on your machine, installing SSDT will
add the full set of SQL Server tools into your existing Visual Studio installation. Visual Studio includes many
features you might want to use, such as Source Code Control integration and non-SQL language support. We
recommend using Visual Studio 2015 Community or above to get the best experience when developing T-SQL.
Supported SQL versions
PROJECT TEMPLATES
SQL PLATFORMS SUPPORTED
Relational databases
SQL Server 2005* - SQL Server 2017
Azure SQL Database
Azure SQL Data Warehouse (supports queries only; database
projects are not yet supported)
* SQL Server 2005 support is deprecated,
please move to an officially supported SQL version
Analysis Services models
SQL Server 2008 – SQL Server 2017
Reporting Services reports
Integration Services packages
SQL Server 2012 – SQL Server 2017
Next steps
After installing SSDT, work through these tutorials to learn how to create databases, packages, data models, and
reports using SSDT:
Project-Oriented Offline Database Development
SSIS Tutorial: Create a Simple ETL Package
Analysis Services tutorials
Create a Basic Table Report (SSRS Tutorial)
Use SSDT in Visual Studio 2017
Download Visual Studio 2017 (compare Visual Studio 2017 features by edition)
To use relational database projects, we recommend checking the Data Storage and Processing workload during
installation. SSDT database project support is also included in a number of other workloads including Azure,
ASP.Net and Web Development, and .Net Core Cross Platform Development.
NOTE
SSDT database projects in Visual Studio 2017 currently support up to SQL Server 2016. Support for SQL Server 2017 will be
coming soon in a Visual Studio 2017 update.
If you are using SSDT with Visual Studio 2017, install the AS and RS components:
Analysis Services
Reporting Services
See Also
SQL Server Data Tools in Visual Studio
SSDT MSDN Forum
SSDT Team Blog
SSDT Connect Feedback
SSDT Documentation
DACFx API Reference
Download SQL Server Management Studio (SSMS)
Changelog for SQL Server Data Tools (SSDT)
4/26/2017 • 24 min to read • Edit Online
This change log is for SQL Server Data Tools (SSDT) for Visual Studio 2015.
For detailed posts about what’s new and changed, please visit the SSDT Team blog.
SSDT 17.0 (supports up to SQL Server 2017)
Build number: 14.0.61704.140
What's New?
Database projects:
Amending a clustered index on a view will no longer block deployment.
Schema comparison strings relating to column encryption will use the proper name rather than the instance
name.
Added a new command line option to SqlPackage: ModelFilePath. This provides an option for advanced users to
specify an external model.xml file for import, publishing and scripting operations.
The DacFx API was extended to support Azure AD Universal Authentication and Multi-factor authentication
(MFA)
IS projects:
The SSIS OData Source and OData Connection Manager now support connecting to the OData feeds of
Microsoft Dynamics AX Online and Microsoft Dynamics CRM Online.
SSIS project now supports target server version of "SQL Server 2017"
Support for CDC Control Task, CDC Splitter and CDC Source when targeting SQL Server 2017.
AS projects:
Analysis Services PowerQuery Integration (1400 compat-level tabular models):
DirectQuery is available for SQL Oracle, And Teradata if user has installed 3rd Party drivers
Add columns by example in PowerQuery
Data access options in 1400 models (model-level properties used by M engine)
Enable fast combine (default is false - when set to true, the mashup engine will ignore data source
privacy levels when combining data)
Enable Legacy Redirects (default is false – when set to true, the mashup engine will follow HTTP
redirects that are potentially insecure. For example, a redirect from an HTTPS to an HTTP URI)
Return Error Values as Null (default is false – when set to true, cell level errors will be returned as
null. When false, an exception will be raised is a cell contains an error)
Additional data sources (file data sources) using PowerQuery
Excel
Text/CSV
Xml
Json
Folder
Access Database
Azure Blob Storage
Localized PowerQuery user interface
DAX Editor Tool Window
Improved DAX editing experience for measures, calculated columns, and detail-rows expressions,
available via the View, Other Windows menu in SSDT
Improvements to DAX parser\Intellisense
RS projects:
Embeddable RVC Control is now available supporting SSRS 2016
Bug fixes
AS projects:
Fixed the template priority for BI Projects so they don’t show up at the top of the New Projects categories in VS
Fixed a VS crash that may occur in rare circumstances when SSIS, SSAS or SSRS solution opened
Tabular: A variety of enhancements and performance fixes for DAX parsing and the formula bar.
Tabular: Tabular Model Explorer will no longer be visible if no SSAS Tabular projects are open.
Multi-dimensional: Fixed an issue where the processing dialog was unusable on High-DPI machines.
Tabular: Fixed an issue where SSDT faults when opening any BI project when SSMS is already open.Connect
Item
Tabular: Fixed an issue where hierarchies were not being properly saved to the bim file in an 1103
model.Connect Item
Tabular: Fixed an issue where Integrated Workspace mode was allowed on 32-bit machines even though it is
not supported.
Tabular: Fixed an issue where clicking on anything while in semi-select mode (typing a DAX expression but
clicking a measure, for example) could cause crashes.
Tabular: Fixed an issue where Deployment Wizard would reset the model's .Name property back to "Model".
Connect Item
Tabular: Fixed an issue where selecting a heirarchy in TME should display properties even if Diagram View is not
selected.
Tabular: Fixed an issue where pasting into the DAX Formula bar would paste images or other content instead of
text when pasting from certain applications.
Tabular: Fixed an issue where some old models in the 1103 couldn't be opened due to presence of measures
with a specific definition.
Tabular: Fixed an issue where XEvent Sessions could not be deleted.
Fixed an issue with attempting to build AS “smproj” files with devenv.com would fail
Fixed an issue that was finalizing text changes too frequently when using the Korean IME in AS tabular model
sheet tab titles
Fixed an issue where the intellisense for DAX Related() function was not working correctly to show columns
from other tables
Improved AS Tabular project import from database dialog by sorting the list of AS databases
Fixed an issue when creating calculated tables in AS tabular model where Tables weren’t listed as suggested
objects in the expression
Fixed an issue in preview 1400 AS models trying to open using Integrated Workspace server after viewing code
Fixed an issue that was preventing some data sources (with no support for initial catalog) from working
correctly in certain circumstances
Deployment Wizard should apply changes to calculated table partitions even when the option to keep partitions
is enabled
Fixed an issue where Advanced Properties dialog to existing AS Connection didn’t show full list until reselected
Fixed a few issues with clipped UI strings that appeared in some localized builds
Fixed a number of issues with PowerQuery integration in 1400 compat-level AS tabular models
Fixed an issue with Report Wizard style templates not showing up correctly
Fixed an issue with the Report Wizard that could lead to incorrect data source settings when changing from SQL
to AS
Fixed an issue causing Analysis Services (Tabular) project build failure from command line (devenv.com\exe)
Fixed an issue with the DAX measure parser to show highlighted and correct text color when starting with
letters before :=
Fixed an issue triggering an ObjectRefException if paths got too long attempting to Show All Files for Tabular
project in integrated workspace mode
Fixed an issue with the Data Source Designer for Compact 4.0 Client Data Provider where it appeared
unavailable
Fixed an issue that caused an error trying to browse AS mining model in VS2017
Fixed an issue in AS multi-dimensional model in VS2017 where DSV diagram stops rendering after changing
views and then hits an exception
Fixed an issue previewing reports with an AS connection failed in VS2017
RS projects:
Fixed an issue when designing reports in SSDT the tree view of parameters, data sources and datasets would
collapse when most changes made
Fixed an issue where Save should save the version of RDL, not the latest version.
Fixed an issue where SSDT RS is backing up files when backup is turned off and several other issues.
Fixed an issue in Report Builder where an error would be shown when clicking "Split Cells". Connect Item
Fixed an issue where caching could cause incorrect data in a report. Connect Item
IS projects:
Fixed an issue that run64bitruntime setting doesn't stick.
Fixed an issue that DataViewer doesn't save displayed columns.
Fixed an issue that Package Parts hides annotations. Connect Item
Fixed an issue that Pacakage Parts discards Data Flow layouts and annotations. Connect Item
Fixed an issue that SSDT crashes when importing project from sql server.
Fixed an issue with Hadoop File System Task TimeoutInMinutes default to 10 after opening saved SSIS package
and at runtime.
Database projects:
SSDT DACPAC deploy add setting back in for IgnoreColumnOrder Connect item
SSDT failing to compile if STRING_SPLIT is used Connect item
Fix issue where DeploymentContributors have access to the public model but the backing schema has not been
initialized Github issue
DacFx temporal fix for FILEGROUP placement
Fix for "Unresolved Reference" error for external synonyms.
Always Encrypted: Online encryption does not disable change tracking on cancellation and does not work
properly if change tracking has not been cleaned prior to start encryption
SSDT 16.5 (supports up to SQL Server 2016)
Released: October 20, 2016
Build number: 14.0.61021.0
What's New?
Connection Improvements
The new search box in the Browse tab helps you filter your Local servers, Network servers, and Azure SQL
databases. This is useful if you have a large number of servers or databases appearing in these lists.
The History tab has right-click menu options to pin / unpin favorites, and a new option to remove connections
from history.
SqlPackage and DacFx API Improvements
Using SqlPackage.exe and the DacFx APIs you can now generate a deployment report, deployment script, and
publish to a database all in one action. This is a timesaver for anyone who likes to keep a report of what was
published during a deployment. Another benefit is that for Azure scenarios, separate scripts for the master
database and the deploy target database are created. Up to now a single script was created which was not useful
for repeated deployments.
For SqlPackage’s Publish and Script actions, two new arguments have been added.
DeployScriptPath (shortname: dsp). This is an optional path to write the deployment script to. For Azure
deployment, if there were TSQL commands to create of modify the DB a master script will be written to the
same path but with “Filename_Master.sql” as the output file name.
DeployReportPath (shortname: drp). This is an optional path to write the deployment report to.
Note that for the Script action, either the existing Output Path arguments or the new script/report-specific
arguments should be used, but not both.
Sample usage:
Publish Action
Sqlpackage.exe /a:Publish /tsn:(localdb)\ProjectsV13 /tdn:MyDatabase /deployscriptpath:”My\DeployScript.sql”
/deployreportpath:”My\DeployReport.xml”
Script Action
Sqlpackage.exe /a:Script /tsn:(localdb)\ProjectsV13 /tdn:MyDatabase /deployscriptpath:”My\DeployScript.sql”
/deployreportpath:”My\DeployReport.xml”
In DacFx, two new APIs have been added: DacServices.Publish() and DacServices.Script(). These also support
performing publish + script + report actions in a single operation. Sample usage:
DacServices service = new DacServices(connectionString);
using(DacPackage package = DacPackage.Load(@"C:\My\db.dacpac")) {
var options = new PublishOptions() {
GenerateDeploymentScript = true, // Should a deployment script be created?
GenerateDeploymentReport = true, // Should an xml deploy report be created?
DatabaseScriptPath = @"C:\My\OutputScript.sql", // optional path to save script to
MasterDbScriptPath = @"C:\My\OutputScript_Master.sql", // optional path to save master script to
DeployOptions = new DacDeployOptions()
};
// Call publish and receive deployment script & report in the results
PublishResult result = service.Publish(package, "TargetDb", options);
Console.WriteLine(result.DatabaseScript);
Console.WriteLine(result.MasterDbScript);
Console.WriteLine(result.DeploymentReport);
// Call script and receive deployment script & report in results
result = service.Script(package, "TargetDb", options);
Console.WriteLine(result.DatabaseScript);
Console.WriteLine(result.MasterDbScript);
Console.WriteLine(result.DeploymentReport);
Analysis Services & Reporting Services
SSAS tabular designer DAX parser has improved performance when working with large DAX expressions. For more
information, please read the Analysis Services blog post.
Fixed / Improved this month
Database Tools
Connect bug 3055711 – Columns cannot be selected from CROSS APPLY OPENJSON with explicit schema
Fixed – issue with Auto-generated History table indexes, where DacFx dropped index on redeployment
Fixed – issue with DacFx batch parser not parsing escaped bracket ‘]’ characters, which caused publish to fail
Improved – SqlPackage now includes descriptions for each action in the help output
Fixed – The “Remember Password” option in the connection dialog was not being preserved when editing
Advanced options and when editing a connection string saved in Publish, Schema Compare and other files
Fixed – For connections show in the History tab with IntegratedAuthentication=true, the Authentication field in
connection properties was left blank. This now shows “Windows Authentication” as expected
Fixed – Changes to the SQL Server Tools Intellisense settings under Tools -> Options -> Text Editor were not
being preserved
Improved – the Pin/Unpin button in the connection dialog History tab is now more compact, reducing the
likelihood of a scrollbar appearing
Fixed – several accessibility issues in the connection dialog were fixed.
Analysis Services & Reporting Services
Fixed an issue in SSDT AS tabular designer where clicking the scrollbar thumb in data grid crashed in certain
situations
Fixed an issue where option to impersonate connection as current user in SSDT AS tabular wasn’t available
Fixed an issue in SSDT AS tabular designer where expanding the formula bar too far could make the project
unable to re-open
Fixed a crash in SSDT AS tabular designer that would occur on key down if table tab was selected
Fixed an issue in SSDT AS projects where Analyze in Excel would not connect to down-level AS server versions
Integration Service
Fixed Connect bug 1608896: Move Multiple Integration Service Package Tasks
SSDT 16.4 (for SQL Server 2016)
Released: September 20, 2016
Build number: 14.0.60918
What's New?
Schema Compare is now supported in SqlPackage.exe and the Data-Tier Application Framework (DacFx) API. For
details, see Schema Compare in SqlPackage and the Data-Tier Application Framework.
Analysis Services – Integrated Workspace Mode for SSDT Tabular (SSAS)
SSDT Tabular now includes an internal SSAS instance, which SSDT Tabular starts automatically in the background if
integrated workspace mode is enabled so that you can add and view tables, columns, and data in the model
designer without having to provide an external workspace server instance. Integrated workspace mode does not
change how SSDT Tabular works with a workspace server and database. What changes is where SSDT Tabular
hosts the workspace database. To enable integrated workspace mode, select the Integrated Workspace option in
the Tabular Model Designer dialog box displayed when creating a new tabular project. For existing tabular projects
that currently use an explicit workspace server, you can switch to integrated workspace mode by setting the
Integrated Workspace Mode parameter to True in the Properties window, which is displayed when you select the
Model.bim file in Solution Explorer. For details, see the Analysis Services blog post.
Updates and fixes Database tools:
Connect Issue 3087775: Temporal tables broken in VS Data Tools July update 14.0.60629.0, "Value cannot be
null. Parameter name: reportedElement"
Connect Issue 1026648: IsPersistedNullable shows as different in SSDT Comparison
Connect Issue 2054735: Identity is reset when importing a BACPAC
Connect Issue 2900167: Running SSDT unit tests leaves temp files behind
Connect Issue 1807712: Backwards compatibility breakage – AppLocal and Nugetization
Analysis Services & Reporting Services
Fixed an issue in SSDT where error tip pop-ups were in the way when editing DAX for DirectQuery calculated
columns.
Fixed an issue in SSDT AS tabular grid where the KPI icon wasn't showing in measure grid when Windows
scaling factor set at high-DPI 200%+.
Fixed an issue in SSDT AS where pasting large table data could make the tabular project unresponsive.
Fixed an issue in SSDT AS tabular model editor to mark the model as needing to save changes when renaming
connection friendly name.
Fixed an issue in the SSDT AS tabular projects where width of columns in the manage relationships dialog could
not be resized.
Fixed an issue in SSDT AS tabular 1200-level models where pasting data from Excel with locale settings like
German didn't treat the comma as the decimal separator correctly.
Fixed an issue in SSDT AS projects with some KPI icon sets which could yield an error "Couldn't retrieve the data
for this visual".
Fixed an issue with SSDT AS project properties dialog to anchored correctly when resized at High-DPI scaling.
Fixed an issue in SSDT AS projects that may have caused an error upgrading certain models with Pasted tables.
Fixed an issue in SSDT AS where pasting full sheet rows from Excel was very slow and created many unwanted
columns.
Fixed an issue in SSDT AS where large static DataTable expressions parsing and highlight was really slow or
appeared to hang.
Fixed an issue in SSDT AS to add measures and KPI values to the current perspective selected in the editor.
Fixed an issue in SSDT where data import into AS project from SQL Azure didn't support schema types other
than "dbo".
SSDT 16.3 (for SQL Server 2016)
Released: August 15, 2016
Build number: 14.0.60812.0
What's New?
Release Versioning & Numbering: Releases are now tagged numerically rather than by month. This aligns
with the new SSMS policy and simplifies cases where we have multiple releases or hotfixes in a month. This
release is 16.3 which means the third update after the RTM release. Any hotfix will be 16.3.1 and so on, with our
next update (planned for next month) being 16.4.
Analysis Services – Tabular Model Explorer: Tabular Model Explorer lets you conveniently navigate through
the various metadata objects in a model, such as data sources, tables, measures, and relationships. It is
implemented as a separate tools window that you can display by opening the View menu in Visual Studio,
pointing to Other Windows, and then clicking Tabular Model Explorer. The Tabular Model Explorer appears by
default in the Solution Explorer area on a separate tab. Tabular Model Explorer organizes the metadata objects
in a tree structure that closely resembles the schema of a tabular 1200 model and many more new features.
Database Tools – Always Encrypted: This release provides new Always Encrypted Key management dialogs
to easily add Column Master Keys or Column Encryption Keys to your database project, or a live database in
SQL Server Object Explorer. This release supports certificates in Windows Certificate Store. In upcoming
releases, Azure Key Vault and CNG Providers will be supported.
While creating Column Master Key or Column Encryption Key, you may experience that the changes are
not reflected on SQL Server Object Explorer immediately after clicking Update Database. To workaround,
refresh the database node in SQL Server Object Explorer.
If you try to encrypt a column in a table with data from SQL Server Object Explorer, you may experience a
failure. This feature is currently supported only in SSDT database projects and SSMS. Support for SQL
Server Object Explorer will be enabled in a later release.
Updates and fixes
Database tools:
SSDT:
Connect bug 1898001 Fixed a column description issue with 128 character limitation.
Fixed an issue where publishing a database from VS did not apply DatabaseServiceObjective
property in the publish profile xml.
Connect bug 2900167 Fixed a unit test issue for incorrectly leaving temp files.
Fixed an issue where Retention Period combo box on Database Settings is truncated.
Fixed an issue for the missing verification of empty old password on SQL CLR project properties
while changing the password.
DACFx:
Fixed an issue where DACFx compatibility level is not updated for SqlAzureV12 error.
Fixed an issue where IsAutoGeneratedHistoryTable property is incorrectly excluded from model
comparison.
Analysis Services & Reporting Services
SSDT:
Fixed an issue that Tabular model cannot be saved when the server connection is lost.
Fixed an issue that SSDT becomes unresponsive due to a possible infinite loop issue in AS.
Fixed a DAX expression issue that caused inconsistent behaviors based on how you commit the
expression .
Fixed a VS crash issue when creating KPIs.
Fixed an issue that generated invalid reports for SQL Server 2008 R2, 2012 and 2014.
Fixed a Hierarchy order issue that caused an infinite loop error for .dwpro project.
Fixed a RS RDL issue where downgrading RDL required a full rebuild which caused user’s
confusion.
Fixed a KPI issue where Hide From Client Tools had no effect.
SSDT July (for SQL Server 2016)
Released: June 30, 2016
Build number: 14.0.60629.0
What's New?
Always Encrypted support: For Databases that contain Always Encrypted columns, this release adds full
support for Always Encrypted through our core APIs and command line tool (SqlPackage.exe). You can build
and publish database projects with full support for all Always Encrypted features.
Temporal Tables enhanced support: Simplified the experience by unlinking temporal tables before
alterations and re-linking once these have completed. This means that Temporal Tables have parity with other
table types (standard, in-memory) in terms of the operations that are supported.
SqlPackage.exe and installation changes: Changes to isolate SSDT from SQL Server engine and SSMS
updates. For details, see Changes to SSDT and SqlPackage.exe installation and updates.
Updates and fixes
Database tools:
From now on SSDT will never disable Transparent Data Encryption (TDE) on a database. Previously since
the default encryption option in a project’s database settings was disabled, it would turn off encryption.
With this fix encryption can be enabled but never disabled during publish.
Increased the retry count and resiliency for Azure SQL DB connections during initial connection.
If the default filegroup is not PRIMARY, Import/Publish to to Azure V12 would fail. Now this setting is
ignored when publishing.
Fixed an issue where when exporting a database with an object with Quoted Identifier on, export
validation could fail in some instances.
Fixed an issue where the TEXTIMAGE_ON option was incorrectly added for Hekaton table creations where
it is not allowed.
Fixed an issue where Export took a long time exporting with large amount of data due to a write to the
model.xml file after data phase completed caused contents of the .bacpac file to be rewritten.
Fixed an issue where Users were not appearing in the Security folder for Azure SQL DW and APS
connections.
Analysis Services & Reporting Services:
Fixed a SxS issue with MSOLAP OLEDB provider where only the 32-bit provider was getting
installed, impacting 64-bit Excel 2016 connecting to SQL Server 2014 (did not repro with
ClickOnce installs from Office365, only MSI Excel install).
Fixed an issue for a corner case to be more robust when upgrading AS model with pasted tables
from 1103 to 1200 compat-level that could give error "Relationship uses an invalid column ID".
Fixed a SxS issue when SSDT-BI 2013 on same machine, could no longer import data in AS model
after uninstalling SSDT 2015 (cartridges shared registry setting).
Improved robustness to address issues\crashes when the connection to the AS engine is lost (i.e.
SSDT left open overnight and AS server recycled, or other cases where the connection is
temporarily lost).
Fixed issues with dialogs opening on different screens than VS in multi-monitor scenarios.
Fixed/enabled support for pasting from HTML tables (grid data) in AS model pasted tables.
Fixed issue where upgrade failed to upgrade an empty pasted table to 1200 (used only as
container table for measures).
Fixed an issue with upgrading AS tabular model with pasted tables to 1200 to work around an AS
engine issue with CalcTables (which are used for Pasted Tables in 1200), to perform a process full
on the new calc tables after the upgrade.
Fixed an issue where canceling creation of new AS 1200 model calculated table with incomplete
DAX expression could crash.
Fixed an issue importing 1200 model from AS server into SSDT AS project when DB name and a
table name were the same.
Fixed an issue with editing KPI measure in 1103 tabular model.
Fixed an Object reference not set exception hit while pasting a KPI measure in the grid for an AS
1200 model.
Fixed an issue where a column in a calculated table could not be deleted from the diagram view in
1200 models.
Fixed an Object Reference not set exception when viewing the model.bim project file properties
while in code view.
Fixed an issue with pasting data into AS model grid to create pasted table yielded incorrect values
on international locales using comma as decimal separator.
Fixed an issue opening 2008 RS project in SSDT and choosing to not upgrade it.
Fixed issue in 1200 compat-level models calculated table UI when using default formatting for
column type to allow changing the formatting type from the UI.
SSDT June (for SQL Server 2016)
Released: June 1, 2016
Build number: 14.0.60525.0
SSDT General Availability (GA) is now released. The SSDT GA update for June 2016 adds support for the latest
updates of SQL Server 2016 RTM, and various bug fixes. For details, see SQL Server Data Tools GA update for June
2016.
SSDT April (for SQL Server 2016 RC3)
Released: April 15, 2016
Build number: 14.0.60413.0
SQL Server Database
Always Encrypted Support: For Databases that contain Always Encrypted columns, SSDT and DacFx allows
viewing and editing these databases and publishing from a database project to them. Note that support for
altering columns with column encryption present will be coming in a future release.
Connection dialog and SQL Server Object Explorer: Multiple fixes and improvements.
The Details page listing advanced connection properties was overhauled to show the full connection
string in a multi-line box, and to improve support on High DPI machines.
We have brought back the traditional error dialog with detailed connection errors. This helps when
diagnosing login issues with clearer error messages and a stack trace so that DBAs or CSS can get the
information they need to help diagnose your problems.
For users with minimal permissions we fixed a number of issues around listing databases in the
Connection Dialog and SQL Server Object Explorer, viewing the Security folder, and more.
Azure SQL DB performance when expanding the databases node to list all DBs has been improved.
SSDT installer:
Fixed issue where .Net was being downloaded on uninstall.
The installer size is now set correctly on High DPI machines.
Removed the version check blocking SSDT installation if a newer SQL Server version is present.
Schema Compare: Fixed a performance issue where checking/unchecking multiple items took a long
time in Visual Studio.
Support for using LocalDB 2014 on x86 machines, since there is no x86 version of SQL Server 2016.
Build and Deployment:
Fixed issue where computed columns were not supported on Temporal Tables.
The “Execute deployment script in single-user mode” option is ignored when deploying to Azure V12 as
this is not supported in cloud scenarios.
SSDT Hotfix (for SQL Server 2016 RC2)
Released: April 5, 2016
Build number: 14.0.60329.0
This build contains a hotfix for the version of SSDT that provides features for SQL Server Integration Services. Build
14.0.60316.0 can also be used with Analysis Services and Reporting Services in SQL Server 2016.
To get this hotfix, use the download links on this blog post.
Report developers, if you build new reports using this build of SSDT, read the known issue and workaround for a
for a temporary issue in SSRS reports found only in this hotfix.
SSDT Hotfix (for SQL Server 2016 RC0)
Released: March 18, 2016
Build number: 14.0.60316.0
This build contains a hotfix for the version of SSDT that provides features for SQL Server 2016 RC0. There is no
RC1 version of SSDT at this time. Build 14.0.60316.0 can be used with either RC0 or RC1 of SQL Server 2016.
SSDT February 2016 Preview (for SQL Server 2016 RC0)
Released: March 7, 2016
Build number: 14.0.60305.0
SQL Server project templates
No announcements for this SSDT preview release. See What's New in Database Engine to learn about other
features in this release.
SSIS package project templates
SSIS Designer creates and maintains packages for SQL Server 2016, 2014, or 2012. New templates renamed
as parts. SSIS Hadoop connector supports for ORC format. See What's New in Integration Services for
details.
SSAS project templates (Tabular model projects)
This month’s update to Analysis Services delivers support for display folders for Tabular models and any
models created with new SQL Server 2016 compatibility level is now supported in SSIS packages. For more
information. see What's New in Analysis Services (blog post) for details.
SSRS report project templates
No announcements for this SSDT preview release. See What's New in Reporting Services to learn about
other features in this release.
SSDT January 2016 Preview
Released: Feb 4, 2016
Build number: 14.0.60203.0
SQL Server project templates
No announcements for this SSDT preview release. See What's New in Database Engine to learn about other
features in this CTP.
SSIS package project templates
Adds support for ODBC source and destination components, a CDC control task,
a CDC source and splitter component, a Microsoft Connector for SAP BW, and an Integration Services
Feature Pack for Azure. See What's New in Integration Services for details.
SSAS project templates
Includes enhancements for Tabular models at 1200 compatibility level, calculated columns and row-level
security for models in DirectQuery mode, translations of model metadata, TMSL script execution in the SSIS
Analysis Services Execute DDL Task, and numerous bug fixes.
See What's New in Analysis Services (msdn) or What's New in Analysis Services (blog post) for details.
SSRS report project templates
No announcements for this SSDT preview release. See What's New in Reporting Services to learn about
other features in this CTP.
SSDT December 2015 Preview
SQL Server project templates include bug fixes for the Connection dialog box, recent history lists, proper
use of authentication context set in the connection property when loading a database list.
Changed test connection timeout value to 15 seconds.
Create an Azure SQL Database server firewall rule if the client IP is not registered when loading a
database list.
SQL Server 2016 CTP3.2 feature programmability support.
SSAS project templates add support for creating calculated tables based on DAX expressions and other
objects already defined in the model.
SSIS package project template additions include SSIS Hadoop connector support for Avro file format and
Kerberos authentication.
Please note that SSIS designer support for SSIS 2012 and 2014 is not yet included in this update.
SSDT November 2015 Preview
SQL Server project templates. Preview of improved connection experience for SQL Server and Azure SQL
Database.
SSIS package project templates. SSIS catalog performance improvement: The performance for most SSIS
catalog views for non-ssis-admin user is improved.
SSAS project templates include enhancements for Tabular model projects in Analysis Services. You can
use the View Code command to view the model definition in JSON. If you aren't using a full-featured
edition Visual Studio 2015, you will need one to get the JSON editor. You can download the Visual Studio
Community edition for free.
SSDT October 2015 Preview
New project templates for BI (Analysis Services models, Reporting Services reports, and Integration Services
packages). All SQL Server project templates are now in one SSDT.
New SSIS features including Hadoop connector, control flow template, relaxed max buffer size of data flow
task.
SQL Server 2016 CTP 3.0 feature support for relational database projects.
Various bug fixes in SSIS and support for Windows 7 OS.
SSDT September 2015 Preview
Multi-language support is new in this preview.
SSDT August 2015 Preview
New standalone Setup.exe program for installing SSDT. You no longer need to use a modified version of SQL
Server Setup. This version of SSDT includes a project template for building relational databases deployed to
SQL Server or Azure SQL Database.
See Also
Download SQL Server Data Tools (SSDT)
Previous releases of SQL Server Data Tools (SSDT and SSDT-BI)
What's New in Database Engine
What's New in Analysis Services
What's New in Integration Services
Data-Tier Application Framework - License Terms
3/14/2017 • 7 min to read • Edit Online
MICROSOFT SOFTWARE LICENSE TERMS
MICROSOFT SQL SERVER DATA-TIER APPLICATION FRAMEWORK
These license terms are an agreement between Microsoft Corporation (or based on where you live, one of its
affiliates) and you. Please read them. They apply to the software named above, which includes the media on which
you received it, if any. The terms also apply to any Microsoft
updates,
supplements,
Internet-based services, and
support services
for this software, unless other terms accompany those items. If so, those terms apply.
BY USING THE SOFTWARE, YOU ACCEPT THESE TERMS. IF YOU DO NOT ACCEPT THEM, DO NOT USE THE
SOFTWARE.
If you comply with these license terms, you have the rights below.
1. INSTALLATION AND USE RIGHTS. You may install and use any number of copies of the software on your
devices to design, develop and test your programs.
2. ADDITIONAL LICENSING REQUIREMENTS AND/OR USE RIGHTS.
a. Distributable Code.
i. Right to Use and Distribute. If you comply with the terms below:
You may copy and distribute the object code form of the software (“Distributable Code”) in programs you
develop; and
You may permit distributors of your programs to copy and distribute the Distributable Code as part of
those programs.
ii. Distribution Requirements. For any Distributable Code you distribute, you must
add significant primary functionality to it in your programs;
for any Distributable Code having a filename extension of .lib, distribute only the results of running such
Distributable Code through a linker with your program;
distribute Distributable Code included in a setup program only as part of that setup program without
modification;
require distributors and external end users to agree to terms that protect it at least as much as this
agreement;
display your valid copyright notice on your programs; and
indemnify, defend, and hold harmless Microsoft from any claims, including attorneys’ fees, related to the
distribution or use of your programs.
iii. Distribution Restrictions. You may not
alter any copyright, trademark or patent notice in the Distributable Code;
use Microsoft’s trademarks in your programs’ names or in a way that suggests your programs come
from or are endorsed by Microsoft;
distribute Distributable Code to run on a platform other than the Windows platform;
include Distributable Code in malicious, deceptive or unlawful programs; or
modify or distribute the source code of any Distributable Code so that any part of it becomes subject to
an Excluded License. An Excluded License is one that requires, as a condition of use, modification or
distribution, that
the code be disclosed or distributed in source code form; or
others have the right to modify it.
3. SCOPE OF LICENSE. The software is licensed, not sold. Unless applicable law gives you more rights,
Microsoft reserves all other rights not expressly granted under this agreement, whether by implication,
estoppel or otherwise. You may use the software only as expressly permitted in this agreement. In doing so,
you must comply with any technical limitations in the software that only allow you to use it in certain ways.
You may not
work around any technical limitations in the software;
reverse engineer, decompile or disassemble the software, except and only to the extent that applicable
law expressly permits, despite this limitation;
make more copies of the software than specified in this agreement or allowed by applicable law, despite
this limitation;
publish the software for others to copy;
rent, lease or lend the software;
transfer the software or this agreement to any third party; or
use the software for commercial software hosting services.
4. THIRD PARTY NOTICES. The software may include third party code, that Microsoft, not the third party,
licenses to you under the terms set forth in this agreement. Notices, if any, for any third party code are
included for your information only. Additionally, any third party scripts, linked to, called or referenced from
this software, are licensed to you by the third parties that own such code, not by Microsoft, see ASP.NET Ajax
CDN Terms of Use: http://www.asp.net/ajaxlibrary/CDN.ashx.
5. BACKUP COPY. You may make one backup copy of the software. You may use it only to reinstall the
software.
6. DOCUMENTATION. Any person that has valid access to your computer or internal network may copy and
use the documentation for your internal, reference purposes.
7. EXPORT RESTRICTIONS. The software is subject to United States export laws and regulations. You must
comply with all domestic and international export laws and regulations that apply to the software. These
laws include restrictions on destinations, end users and end use. For additional information, see
www.microsoft.com/exporting.
8. SUPPORT SERVICES. Because this software is “as is,” we may not provide support services for it.
9. ENTIRE AGREEMENT. This agreement, and the terms for supplements, updates, Internet-based services and
support services that you use, are the entire agreement for the software and support services.
10. APPLICABLE LAW.
a. United States. If you acquired the software in the United States, Washington state law governs the
interpretation of this agreement and applies to claims for breach of it, regardless of conflict of laws
principles. The laws of the state where you live govern all other claims, including claims under state
consumer protection laws, unfair competition laws, and in tort.
b. Outside the United States. If you acquired the software in any other country, the laws of that country
apply.
11. LEGAL EFFECT. This agreement describes certain legal rights. You may have other rights under the laws of
your country. You may also have rights with respect to the party from whom you acquired the software. This
agreement does not change your rights under the laws of your country if the laws of your country do not
permit it to do so.
12. DISCLAIMER OF WARRANTY. THE SOFTWARE IS LICENSED “AS-IS.” YOU BEAR THE RISK OF USING
IT. MICROSOFT GIVES NO EXPRESS WARRANTIES, GUARANTEES OR CONDITIONS. YOU MAY HAVE
ADDITIONAL CONSUMER RIGHTS OR STATUTORY GUARANTEES UNDER YOUR LOCAL LAWS WHICH
THIS AGREEMENT CANNOT CHANGE. TO THE EXTENT PERMITTED UNDER YOUR LOCAL LAWS,
MICROSOFT EXCLUDES THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NON-INFRINGEMENT.
FOR AUSTRALIA – YOU HAVE STATUTORY GUARANTEES UNDER THE AUSTRALIAN CONSUMER LAW
AND NOTHING IN THESE TERMS IS INTENDED TO AFFECT THOSE RIGHTS.
13. LIMITATION ON AND EXCLUSION OF REMEDIES AND DAMAGES. YOU CAN RECOVER FROM
MICROSOFT AND ITS SUPPLIERS ONLY DIRECT DAMAGES UP TO U.S. $5.00. YOU CANNOT RECOVER
ANY OTHER DAMAGES, INCLUDING CONSEQUENTIAL, LOST PROFITS, SPECIAL, INDIRECT OR
INCIDENTAL DAMAGES.
This limitation applies to
anything related to the software, services, content (including code) on third party Internet sites, or third party
programs; and
claims for breach of contract, breach of warranty, guarantee or condition, strict liability, negligence, or other tort
to the extent permitted by applicable law.
It also applies even if Microsoft knew or should have known about the possibility of the damages. The above
limitation or exclusion may not apply to you because your country may not allow the exclusion or limitation of
incidental, consequential or other damages.
Please note: As this software is distributed in Quebec, Canada, some of these license terms are provided
below in French.
Remarque : Ce logiciel étant distribué au Québec, Canada, les termes de cette licence sont fournis cidessous en français.
EXCLUSIONS DE GARANTIE. Le logiciel est concédé sous licence « en l’état ». Vous assumez tous
les risques liés à son utilisation. Microsoft n’accorde aucune garantie ou condition expresse. Vous
pouvez bénéficier de droits des consommateurs supplémentaires ou de garanties statutaires dans
le cadre du droit local, que ce contrat ne peut modifier. Lorsque cela est autorisé par le droit local,
Microsoft exclut les garanties implicites de qualité, d’adéquation à un usage particulier et
d’absence de contrefaçon.
POUR L’AUSTRALIE – La loi australienne sur la consommation (Australian Consumer Law) vous
accorde des garanties statutaires qu’aucun élément du présent accord ne peut affecter.
LIMITATION ET EXCLUSION DE RECOURS ET DE DOMMAGES. Vous pouvez obtenir de Microsoft et
de ses fournisseurs une indemnisation en cas de dommages directs limitée uniquement à hauteur
de 5,00 $ US. Vous ne pouvez prétendre à aucune indemnisation pour les autres dommages, y
compris les dommages spéciaux, indirects ou accessoires et pertes de bénéfices.
Cette limitation concerne:
toute affaire liée au logiciel, aux services ou au contenu (y compris le code) figurant sur des sites Internet
tiers ou dans des programmes tiers et
les réclamations au titre de violation de contrat ou de garantie, ou au titre de responsabilité stricte, de
négligence ou d’une autre faute dans la limite autorisée par la loi en vigueur.
Elle s’applique également même si Microsoft connaissait l'éventualité d'un tel dommage. La limitation ou exclusion
ci-dessus peut également ne pas vous être applicable, car votre pays n’autorise pas l’exclusion ou la limitation de
responsabilité pour les dommages indirects, accessoires ou de quelque nature que ce soit.
Previous releases of SQL Server Data Tools (SSDT
and SSDT-BI)
3/14/2017 • 2 min to read • Edit Online
SQL Server Data Tools (SSDT) provides project templates and design surfaces for building SQL Server content
types — relational databases, Analysis Services models, Reporting Services reports, and Integration Services
packages.
It's based on a Visual Studio shell and co-released with SQL Server. New versions of SSDT integrate the very latest
features of SQL Server. Older versions include the templates and design environment that were current for that
release.
SSDT is backwards compatible, which means you can always use the newest SSDT to design and deploy databases,
models, reports, and packages that run on older versions of SQL Server. You can also use any of the previously
released versions listed below.
NOTE
Historically, the Visual Studio shell used to create SQL Server content types has been released under various names, including
SQL Server Data Tools, SQL Server Data Tools - Business Intelligence, and Business Intelligence Development
Studio. Previous versions came with distinct sets of project templates. To get all of the project templates together in one
SSDT, you need the newest version. Otherwise, you will probably need to install multiple previous versions to get all of the
templates used in SQL Server. Only one shell will be installed per version of Visual Studio; installing a second SSDT just adds
the missing templates.
Recent downloads
The last three recent downloads are provided for the unlikely event that you experience issues with the latest
release.
RELEASE
VISUAL STUDIO 2015
VISUAL STUDIO 2013
16.5
SSDT for VS2015 16.5
SSDT for VS2013 16.5
16.4.1
SSDT for VS2015 16.4.1
SSDT for VS2013 16.4.1
16.3
SSDT for VS2015 16.3
SSDT for VS2013 16.3
Links to Download pages
SQL Relational: Database Engine
Provides templates for building relational databases for the RDBMS and Azure SQL Database. SSDT is version
agnostic with respect to relational database design. You can use either the Visual Studio 2012 or 2013 version with
any version of SQL Server Database Engine or Azure SQL Database.
Database Designers
Download SSDT for Visual Studio 2013
Download SSDT for Visual Studio 2012
SSDT for Visual Studio 2010 is no longer available so please choose a newer version. Newer versions of
SSDT will run side-by-side your existing Visual Studio 2010 installation. It's not necessary to have SSDT
match the full-product version of Visual Studio on your computer.
Visual Studio 2013 customers can download a preview version of SSDT to try out new features that are not yet in
the product release version.
SQL BI: Analysis Services, Reporting Services, Integration services
BI templates are used to create SSAS models, SSRS reports, and SSIS packages. BI Designers are tied to specific
releases of SQL Server. To use the newer BI features, install a newer versioned BI designer.
BI Designers
Download SSDT-BI for Visual Studio 2013: SQL Server 2014, SQL Server 2012, SQL Server 2008 and 2008 R2
Download SSDT-BI for Visual Studio 2012: SQL Server 2014, SQL Server 2012, SQL Server 2008 and 2008 R2
Business Intelligence Development Studio (BIDS) -BIDS is installed via SQL Server Setup. There is no web
download.: SQL Server 2008 and 2008 R2
For SQL Server 2012 or 2014, you can use either SSDT-BI for Visual Studio 2012 or SSDT-BI for Visual Studio
2013. The only difference is between the two is the Visual Studio version.
See Also
Download SQL Server Data Tools (SSDT)
Download SQL Server Management Studio (SSMS)
SQL Server Tools
3/14/2017 • 1 min to read • Edit Online
Download the tools
Download SQL Server Management Studio (SSMS)
Download SQL Server Data Tools (SSDT)
Learn
SQL Server Management Tools (including SSMS)
Use SQL Server Management Studio
See Also
SQL Server Drivers
SQL Server Data Tools - License Terms
3/14/2017 • 10 min to read • Edit Online
MICROSOFT SOFTWARE LICENSE TERMS
MICROSOFT SQL SERVER DATA TOOLS
These license terms are an agreement between Microsoft Corporation (or based on where you live, one of its
affiliates) and you. Please read them. They apply to the software named above, which includes the media on which
you received it, if any. The terms also apply to any Microsoft
updates,
supplements,
Internet-based services, and
support services
for this software, unless other terms accompany those items. If so, those terms apply.
BY USING THE SOFTWARE, YOU ACCEPT THESE TERMS. YOU MAY CHOOSE NOT TO ACCEPT THESE TERMS,
IN WHICH CASE YOU MAY NOT USE THE SOFTWARE (IF YOU HAVE NOT ALREADY INSTALLED IT) OR
WITHDRAW YOUR ACCEPTANCE ANY TIME BY UNINSTALLING THE SOFTWARE.
If you comply with these license terms, you have the rights below.
1. INSTALLATION AND USE RIGHTS.
a. Installation and Use.
You may install and use any number of copies of the software on your devices to design, develop and test your
programs.
b. Other Microsoft Programs. The software includes other Microsoft SQL Server technologies, Microsoft Visual
Studio 2015 Shell (Isolated) Redistributable Package, Microsoft Visual Studio 2015 Shell (Integrated)
Redistributable Package, Microsoft Visual Studio Tools for Applications 2015, .NET Framework, Visual C++
Redistributable for Visual Studio 2015, and Microsoft Report Viewer 2016 Runtime in conjunction with the
software licensed here. These components are governed by separate agreements and their own product support
policies, as described in the license terms found in the installation directory for that component or in the “Licenses”
folder accompanying the software.
2. ADDITIONAL LICENSING REQUIREMENTS AND/OR USE RIGHTS.
a. Distributable Code.
i. Right to Use and Distribute. If you comply with the terms below:
You may copy and distribute the object code form of the Microsoft SQL Server Data-Tier Application Framework
(“Distributable Code”) in programs you develop; and
You may permit distributors of your programs to copy and distribute the Distributable Code as part of those
programs.
ii. Distribution Requirements. For any Distributable Code you distribute, you must
add significant primary functionality to it in your programs;
for any Distributable Code having a filename extension of .lib, distribute only the results of running such
Distributable Code through a linker with your program;
distribute Distributable Code included in a setup program only as part of that setup program without
modification;
require distributors and external end users to agree to the Microsoft license terms included as part of our
software setup program;
display your valid copyright notice on your programs; and
indemnify, defend, and hold harmless Microsoft from any claims, including attorneys’ fees, related to the
distribution or use of your programs.
iii. Distribution Restrictions. You may not
alter any copyright, trademark or patent notice in the Distributable Code;
use Microsoft’s trademarks in your programs’ names or in a way that suggests your programs come from or
are endorsed by Microsoft;
distribute Distributable Code to run on a platform other than the Windows platform;
include Distributable Code in malicious, deceptive or unlawful programs; or
modify or distribute the source code of any Distributable Code so that any part of it becomes subject to an
Excluded License. An Excluded License is one that requires, as a condition of use, modification or distribution,
that
the code be disclosed or distributed in source code form; or
others have the right to modify it.
3. INTERNET-BASED SERVICES. Microsoft provides Internet-based services with the software. It may change or
cancel them at any time. You may not use these devices in any way that could harm them or impair anyone else’s
use of them. You may not use the services to try to gain unauthorized access to any service, data, account or
network by any means.
a. SQL Server Reporting Services Map Report Item. The software may include features that retrieve content
such as maps, images and other data through the Bing Maps (or successor branded) application programming
interface (the “Bing Maps APIs”). The purpose of these features is to create reports displaying data on top of maps,
aerial and hybrid imagery. If these features are included, you may use them to create and view dynamic or static
documents. This may be done only in conjunction with and through methods and means of access integrated in the
software. You may not otherwise copy, store, archive, or create a database of the content available through the Bing
Maps APIs. You may not use the following for any purpose even if they are available through the Bing Maps APIs:
Bing Maps APIs to provide sensor based guidance/routing, or
any Road Traffic Data or Bird’s Eye Imagery (or associated metadata).
Your use of Bing Maps is also governed by the Bing Maps End User Terms of Use available at
http://go.microsoft.com/?linkid=9710837 and the Bing Maps Privacy Statement available at
http://go.microsoft.com/fwlink/?LinkID=248686.
b. This software is designed to allow users of SQL Server Integration Services (SSIS) to (a) move data between onpremises data-stores and Microsoft online services and (b) trigger certain actions in Microsoft online services. In
order to do this, the software uses Internet Protocols to (i) send data, including your own data as designated by you
and data about the software’s configuration, to these services, and (ii) request data, including your own data as
designated by you and data about the nature and configuration of your Microsoft online services, from these
services. Once you configure the software to communicate with these services, you may not receive separate
notices when the software connects to these services.
4. FEEDBACK. If you give feedback about the software to Microsoft, you give to Microsoft, without charge, the right
to use, share and commercialize your feedback in any way and for any purpose. You also give to third parties,
without charge, any patent rights needed for their products, technologies and services to use or interface with any
specific parts of a Microsoft software or service that includes the feedback. You will not give feedback that is subject
to a license that requires Microsoft to license its software or documentation to third parties because we include
your feedback in them. These rights survive this agreement.
5. THIRD PARTY NOTICES. The software may include third party components with separate legal notices or
governed by other agreements, as may be described in the ThirdPartyNotices file accompanying the software. Even
if such components are governed by other agreements, the disclaimers and the limitations on and exclusions of
damages below also apply.
6. .NET FRAMEWORK SOFTWARE. The software contains Microsoft .NET Framework software. This software is
part of Windows. The license terms for Windows apply to your use of the .NET Framework software.
7. SCOPE OF LICENSE. The software is licensed, not sold. This agreement only gives you some rights to use the
software. Microsoft reserves all other rights. Unless applicable law gives you more rights despite this limitation, you
may use the software only as expressly permitted in this agreement. In doing so, you must comply with any
technical limitations in the software that only allow you to use it in certain ways. You may not
disclose the results of any benchmark tests of the software, other than the Microsoft .NET Framework (see
separate term above), to any third party without Microsoft’s prior written approval;
work around any technical limitations in the software;
reverse engineer, decompile or disassemble the software, except and only to the extent that applicable law
expressly permits, despite this limitation;
make more copies of the software than specified in this agreement or allowed by applicable law, despite this
limitation;
publish the software for others to copy;
rent, lease or lend the software;
transfer the software or this agreement to any third party; or
use the software for commercial software hosting services.
8. EXPORT RESTRICTIONS. The software is subject to United States export laws and regulations. You must comply
with all domestic and international export laws and regulations that apply to the software. These laws include
restrictions on destinations, end users and end use. For additional information, see www.microsoft.com/exporting.
9. UPDATES. The software may install automatic updates, which cannot be turned off. By using the software, you
agree to receive automatic updates without any additional notice, and permit Microsoft to download and install
them for you. You agree to obtain these updates only from Microsoft or Microsoft authorized sources. If you do not
want software updates, disconnect your device from the internet or uninstall the software.
10. SUPPORT SERVICES. Because this software is “as is,” we may not provide support services for it.
11. ENTIRE AGREEMENT. This agreement, and the terms for supplements, updates, Internet-based services and
support services that you use, are the entire agreement for the software and support services.
12. APPLICABLE LAW.
a. United States. If you acquired the software in the United States, Washington state law governs the
interpretation of this agreement and applies to claims for breach of it, regardless of conflict of laws principles. The
laws of the state where you live govern all other claims, including claims under state consumer protection laws,
unfair competition laws, and in tort.
b. Outside the United States. If you acquired the software in any other country, the laws of that country apply.
13. LEGAL EFFECT. This agreement describes certain legal rights. You may have other rights under the laws of your
country. You may also have rights with respect to the party from whom you acquired the software. This agreement
does not change your rights under the laws of your country if the laws of your country do not permit it to do so.
14. DISCLAIMER OF WARRANTY. The software is licensed “as-is.” You bear the risk of using it. Microsoft
gives no express warranties, guarantees or conditions. You may have additional consumer rights or
statutory guarantees under your local laws which this agreement cannot change. To the extent
permitted under your local laws, Microsoft excludes the implied warranties of merchantability, fitness
for a particular purpose and non-infringement.
FOR AUSTRALIA – You have statutory guarantees under the Australian Consumer Law and nothing in these terms
is intended to affect those rights.
15. LIMITATION ON AND EXCLUSION OF REMEDIES AND DAMAGES. You can recover from Microsoft and
its suppliers only direct damages up to U.S. $5.00. You cannot recover any other damages, including
consequential, lost profits, special, indirect or incidental damages.
This limitation applies to
anything related to the software, services, content (including code) on third party Internet sites, or third party
programs; and
claims for breach of contract, breach of warranty, guarantee or condition, strict liability, negligence, or other tort
to the extent permitted by applicable law.
It also applies even if Microsoft knew or should have known about the possibility of the damages. The above
limitation or exclusion may not apply to you because your country may not allow the exclusion or limitation of
incidental, consequential or other damages.
Please note: As this software is distributed in Quebec, Canada, these license terms are provided below in
French.
Remarque : Ce logiciel étant distribué au Québec, Canada, certaines des clauses dans ce contrat sont
fournies ci-dessous en français.
EXCLUSIONS DE GARANTIE. Le logiciel est concédé sous licence « en l’état ». Vous assumez tous les risques liés à
son utilisation. Microsoft n’accorde aucune garantie ou condition expresse. Vous pouvez bénéficier de droits des
consommateurs supplémentaires dans le cadre du droit local, que ce contrat ne peut modifier. Lorsque cela est
autorisé par le droit local, Microsoft exclut les garanties implicites de qualité, d’adéquation à un usage particulier et
d’absence de contrefaçon.
LIMITATION ET EXCLUSION DE RECOURS ET DE DOMMAGES. Vous pouvez obtenir de Microsoft et de ses
fournisseurs une indemnisation en cas de dommages directs limitée uniquement à hauteur de 5,00 $ US. Vous ne
pouvez prétendre à aucune indemnisation pour les autres dommages, y compris les dommages spéciaux, indirects
ou accessoires et pertes de bénéfices.
Cette limitation concerne :
toute affaire liée au logiciel, aux services ou au contenu (y compris le code) figurant sur des sites Internet tiers ou
dans des programmes tiers et
les réclamations au titre de violation de contrat ou de garantie, ou au titre de responsabilité stricte, de négligence
ou d’une autre faute dans la limite autorisée par la loi en vigueur.
Elle s’applique également même si Microsoft connaissait l'éventualité d'un tel dommage. La limitation ou exclusion
ci-dessus peut également ne pas vous être applicable, car votre pays n’autorise pas l’exclusion ou la limitation de
responsabilité pour les dommages indirects, accessoires ou de quelque nature que ce soit.
EFFET JURIDIQUE. Le présent contrat décrit certains droits juridiques. Vous pourriez avoir d’autres droits prévus par
les lois de votre pays. Le présent contrat ne modifie pas les droits que vous confèrent les lois de votre pays si cellesci ne le permettent pas.