As pictured below (using SSMS 2016 CTP 3.1) I have 2 Columns folders under each table... I've tried restarting SSMS, etc... they persist. What's going on?
Looks like the issue has been fixed in SSMS, but won't be available until after the 3.2 (SSMS December preview) release. Source: Microsoft connect item
Related
I have been encountering all sort of problems to istall the SQL Server 2019 Express as well as SSMS v. 18.9. I wanted to move from SSQLSERVER 2014 and SSMS 2014 to 2019 version in order to attend a course on T-SQL using the latest version of the software.
After unstalling 2014 Server and Management studio files, I have been unable to install the 2019 version, either the Basic installation (the error says that "there has been an error when checking the installation rules for SQL Server"), or by downloading the resources (in this case, when I click on the setup.exe file a error dialog window appears with a red X saying "SQL Server setup").
Any tips, please?
Thanks in advance.
I have some SQL CLR projects I created with VS 2012. I want to open them with VS 2013, so I installed SSDT 16.5 for VS 2013.
Now, I am getting this error opening the SQL CLR projects:
Could not load file or assembly 'Microsoft.SqlServer.Management.SqlParser, Version=13.0.0.0
Thanks for any ideas
I also faced this issue, Installing SQL Server 2017 broke SSDT. I have fixed the issue, Here is how I was able to fix it
Steps
Uninstall Microsoft SQL Server 2017 TSQL Language Service.
Install TSqlLanguageService.msi from SQL Server 2016. Part of Microsoft® SQL
Server® 2016 Feature Pack - https://www.microsoft.com/en-us/download/details.aspx?id=52676 (Version:13.0.1601.5 File: ENU\x64\TSqlLanguageService.msi)
then restart visual studio and reload the project
Installing a newer version of SQL Server Management Studio can break SQL Server Data Tools. You need to downgrade the TSQL Language service to 2016 (13.0.0.0) level.
Originally from here:
https://www.sqlservercentral.com/Forums/1921984/Microsoft-Visual-Studio-Could-not-load-file-or-assembly-MicrosoftSqlServerManagementSqlParser-Versio
Installing SQL Server 2017 broke SSDT. I have fixed the issue, but
just wanted to post this because I couldn't find the solution at
first. Steps
Uninstall Microsoft SQL Server 2017 TSQL Language Service.
Install TSqlLanguageService.msi from SQL Server 2016.
Part of Microsoft® SQL Server® 2016 Feature Pack - https://www.microsoft.com/en-us/download/details.aspx?id=52676
Version:13.0.1601.5
File: ENU\x64\TSqlLanguageService.msi
I hope this helps someone.
https://connect.microsoft.com/SQLServer/feedback/details/3106613/net-exception-could-not-load-file-or-assembly-microsoft-sqlserver-sqlclrprovider-13-100-0-0-after-installing-sql-server-2016
Client applications should not be using the assemblies from the Program Files folders unless they are from the specific SDK folders (such as "C:\Program Files (x86)\Microsoft SQL Server\130\SDK")
The 13.100.* version of assemblies you are seeing are currently only for use by Microsoft tools and so are not placed with all needed dependencies being in the same place. The DTS folder especially has only a subset of SMO assemblies since that code does not need things such as SqlClrProvider.
Please use either the assemblies from the SDK folders or from SharedManagementObjects.msi to use as references for your applications.
I have VS 2017 CE, SQL Server 2016 DE and Microsoft SQL Server Management Studio 13.0.16106.4. About VS is showing Microsoft SQL Server Data Tools as installed.
I would like to install SSDT so that I can do the SSRS/SSIS and SSAS but I don't know which one to install, it's giving few options from here
It reads
Download SQL Server Data Tools 17.1 for Visual Studio 2015
Download Data-Tier Application Framework (DacFx) 17.1
From the same website
It then advises "To use SQL Server Data Tools in Visual Studio 2017 see this section below". When I go to the link provided it takes me to visualstudio.com website. It's not apparent to me what I need to download from there, is it the Community Edition?
Going back to the first link I provided, it advises...
If you are using SSDT with Visual Studio 2017, install the AS and RS components:
Analysis Services
Reporting Services
I also found another link...www.visualstudio.com/vs/ssdt/
Also are there any conflict between sql server 2016 and vs 2017 CE when taking SSRS/SSIS or SSAS tasks?
StackOverFlow is giving me message that I need to have number of reputation before I can give more than 1 website link.
Can someone advise me which one to install?
Thanks.
For Visual Studio 2017, there is not yet a stand alone install of SSIS|AS|RS. However, there are VSIX installs available for RS and AS. See links below.
SSIS is working on creating a standalone install as well as a VSIX package.
https://marketplace.visualstudio.com/items?itemName=ProBITools.MicrosoftReportProjectsforVisualStudio
https://marketplace.visualstudio.com/items?itemName=ProBITools.MicrosoftAnalysisServicesModelingProjects
I have installed SQL Server Data Tools for Business Intelligence (SSDT-BI) version 14.0.61705.170 and SQL Server Reporting Services (SSRS) version 14.0.608.142.
I'm trying to upgrade and edit a collection of older report files for use with the current version of SSRS. The project upgrades (apparently) ok, and the reports are viewable in the SSDT-BI report editor.
But whenever I try to save any of these reports, an error message box pops up which says "Unknown Report Version: 9.0".
I suspect it's because the RDL files are so old, but I don't see 9.0 anywhere in the RDL file so I'm not sure what I need to tweak to make the files savable again. Perhaps an XML schema name or similar?
The main namespace in the RDL files is currently http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition
"Version 9.0" probably corresponds to SQL Server 2005 since that was the major version number of that release of SQL Server, and 2005 can be found in the schema namespace.
This document says that:
Reports that were created in any previous version of Reporting
Services can be upgraded. This includes the following versions:
SQL Server 2008
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014
So... how can I upgrade these reports for full compatibility with modern SSRS versions?
I downloaded "SQL Server 2012 Express with Advanced Services" from MSDN and installed the SSRS report editing tools, and then used those to open & save the reports. (It also works to download SSDT-BI for Visual Studio 2012 (version 11.0.5583.0) by following links on this Microsoft web page. This installs a different version of the SSRS editors, based on VS2012 instead of VS2010.)
This upgraded the .rdl files from the 2005 reports schema to the 2008 reports schema (I suppose there were no actual schema changes between SSRS 2008, 2008 R2, and 2012).
The upgraded reports could then be opened and edited in the SQL Server 2016 tools, which upgrades them again, to the SSRS 2016 schema.
I followed these steps to migrate old reports. Opened the old SSRS report project in VS2017 (not the solution file). It asks for the migration. Then open the rdl file in designer mode, it will upgrade the definition schema of the report. Save the report. You can then open the project file either in VS2015 or VS2017 with upgraded report definition schema.
I am using Windows 7 SP1.
I have SQL Server 2012 installed along with Visual Studio Community 2015.
The SQL Server 2012 installation has always forced me to use VS2010 Shell to launch SQL Server Data Tools.
I recently installed an update through the NuGet Package Manager in VS2015 which included SSDT. I was hoping that this would enable me to use SSDT with VS2015. However it still launches with VS2010.
My question is: How do I used SQL Server Data Tools with Visual Studio 2015?
Thanks
The latest release (Feb 2016) is the first release of SSDT that can target different versions of SSIS so you can now target 2012 from visual studio 2015:
https://blogs.msdn.microsoft.com/ssdt/2016/03/07/ssdt-preview-update-feb-2016/
It is still in preview though so you will need to download the pre-release bits:
https://msdn.microsoft.com/en-us/library/mt204009.aspx
or wait a month or so for the RTM release.
I usually use the pre-release builds and they are normally pretty solid but each environment is different :)
ed