Am trying to use the Import and Export Wizard within Microsoft SQL Server Management Studio (right click database name > Tasks > Import Data) but immediately get this error;
SQL Server Import and Export Wizard has stopped working
This process has been working fine until this week when IT have upgraded us from MSSMS v17.6 to v18.9 (component and version info below)
SQL Server Management Studio 15.0.18382.0
SQL Server Management Objects (SMO) 16.100.46337.53
Microsoft Analysis Services Client Tools 15.0.19535.0
Microsoft Data Access Components (MDAC) 10.0.19041.1
Microsoft MSXML 3.0 6.0
Microsoft .NET Framework 4.0.30319.42000
Operating System 10.0.19044
IT are unable to troubleshoot and resolve the problem, but I'm guessing something is wrong with the install of the newer version of MSSMS. Any ideas or assistance to aid resolution gratefully received.
It happened to me, too. I read some threads saying that if you install SQL Server Data Tool, the wizard and SQL Job property window stop working altogether. Launching the wizard within Visual Studio works fine.
Related
On my PC, I messed up the default installation of the SQL Server that comes with VS22.
I managed to install SQL Server manually again, but I have to write a database class library using EF Core.
For that I have a connection string as follows:
Data Source=(localdb)\\MSSQLLOCALDB;Initial Catalog=TestDB;Integrated Security=True
I've been told that EF will create the database as needed after the name given in the connection string.
This works fine on my new laptop on which I did not touch the SQL Server. On my PC it does not work though.
What do I have to do to get the "default" installation of the SQL Server?
You can install LocalDB through the Visual Studio Installer, as part of the Data Storage and Processing workload, the ASP.NET and web development workload, or as an individual component.
The steps in Visual Studio Installer are as follows:
First select Modity, then select SQL Server Express LocalDB in Installation details. Hope it helps you.
I tried to import my db from SQL Azure, but I am getting the next error in SQL Server Management Studio from each version that I specified:
SQL Server Management Studio v17.9.1:
Could not load schema model from package. (Microsoft.SqlServer.Dac)
ADDITIONAL INFORMATION:
Internal Error. The database platform service with type Microsoft.Data.Tools.Schema.Sql.Sql150DatabaseSchemaProvider is not valid.
You must make sure the service is loaded, or you must provide the full type name of a valid database platform service.
(Microsoft.Data.Tools.Schema.Sql)
SQL Server Management Studio v18.0 Preview 5:
Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)
ADDITIONAL INFORMATION:
There is already an open DataReader associated with this Command which must be closed first. (System.Data)
The version when I am trying to import SQL Server is
Uninstall SQL Server Management Studio 2018, then install SSMS v17.9.1. Re-import the Bacpac and you will have better results.
For this import error, you can try this way :
Install Microsoft SQL Server Data-Tier Application Framework (February 2015) ( Both the x64 and x86 versions).
Here is the link may be useful for you:
Unable to import SQL Azure V12 BACPAC: "type Microsoft.Data.Tools.Schema.Sql.SqlAzureV12DatabaseSchemaProvider is not valid"
I've actually been having a very similar problem.
Although I had a slightly different error message for MSSMSv17 (in regards to the additional information).
But the same error for MSSMSv18 (Preview 6).
So after trying many different things until I had irreversible damaged my SQL server installations to the point where I had to reinstall Windows, the first thing I installed was SQL Server 2017 & MSSMSv18. Which produced the same error as before. But MSSMSv17 worked, soo... yay?
Hi I'm looking for some guidance.
I've developed an SSIS project with a couple of script tasks and script components using visual studio 2015 for targeted version 2016.
I have two environment server A and server B both have SSIS 2016 SP1 installed on it.
I have done a project deployed of the packages to Sever A and tested the packages everything executed perfectly.
However when I deployed the packages in SSIS_DB from Server A to Server B I get these errors in my execution report.
The component metadata for "script component, clsid { }" could not be upgraded to the newer version of the component. The PerformUpgrade method failed
2
There was an exception while loading Script Task from XML: System.Exception: The Script Task "" uses version 15.0 script that is not supported in this release of Integration Services. To run the package, use the Script Task to create a new VSTA script. In most cases, scripts are converted automatically to use a supported version, when you open a SQL Server Integration Services package in %SQL_PRODUCT_SHORT_NAME% Integration Services.
at Microsoft.SqlServer.Dts.Tasks.ScriptTask.ScriptTask.LoadFromXML(XmlElement elemProj, IDTSInfoEvents events)
The interesting part is if I deploy my packages directly from visual studio to Server B the packages executes correctly with no issue.
So there seems to be inconsistencies between server A and Server B.
A small background to this is that when both servers were built Server A had Microsoft SQL Server 2016 (SP1-GDR) and Server Microsoft SQL Server 2016 (RTM)
but they both now have Microsoft SQL Server 2016 (SP1-GDR) after Server B was updated.
I'm not sure how the upgrade was done by my suspicion is that the SSIS on server are different but I can't seem to prove it.
when I check the version they both seem to return same or similar meta data
The right answer is here: https://andyleonard.blog/2017/09/ssis-version-15-0-script-error/
In my case the problem was the setting at the project level “TargetServerLevel” set to “SQL Server 2017”. The correct value must be “SQL Server 2016”. Once the value is changed and the project redeployed errors desappear.
I believe one of developers in my team used VS 2017 when added the project. All other tasks and components, excep script, were fine even with incorrect server version and the problem appeared only when I had to use script tasks and components.
To fix the problem open project parameters => Configuration Properties => TargetServerVersion
Select “SQL Server 2016”, then deploy to the server.
This was caused by SSMS. I don’t know what’s going on under the hood but During the deployment I was using SSMS 2017 which seems to be upgrading script components in my packages. I changed to use SSMS 2016 and this issue disappeared
Just summarizing some things because there are some reasons for facing this problem:
Your are deploying a package with Target Version Definition for another SQL Server
You are deploying a package which contains a script task with not same SSMS version as SQL Server Version
If your package doesn't contain a script task for example, then any version of SSMS can deploy the package to any version of SQL Server via SSISDB catalog. Not sure why is this happening. Seems that you can deploy and execute packages while making sure that the package target version is supported from SQL Version, but also if you have a ScriptTask inside you need to be super careful and make sure also that the integration services version of SSMS is the same with SQL Server version.
I will open a question to Microsoft just to be sure why the script task has this treatment. Maybe is because the script task is Framework dependent.
I am not able to connect to SQL Server .dbml file. When I am trying to connect to SQL Server, it shows a message to "install the missing package". Now, when I am installing that missing plug-in, it just shows the progress bar and at last shows "Installation completed". But again when I try to connect, it shows the above error message.
Can anyone please help me to install it manually?
Step 1:
Step 2:
Step 3:
Search for and install the latest version of SSDT (Sql Server Data Tools).
I install Visual Studio (community edition) quite often and this happened to one of the PCs I develop on.
Uninstalling/Re-installing Visual Studio is what make this work.
Starting with Visual Studio 2017, the functionality of creating Database Projects has been integrated into the Visual Studio installation. There is no need to install the SSDT standalone installer for the core SSDT experience. To create Integration Services/Analysis Services/Reporting Services projects you still need the SSDT standalone installer.
For Database Projects, install the Data Storage and Processing workload for Visual Studio
For Analysis Services, Integration Services or Reporting Services projects, download and install SQL Server Data Tools
I'd like to be able to use a Visual Studio Database Project against an Oracle server.
I can successfully connect it against an instance of SQL Server with no problems, however when I attempt to connect to Oracle the datasource button is greyed out:
I sincerely hope that it's possible to use this against Oracle. However if not are there any alternatives / workarounds.
You will need to install the following:
Oracle Data Provider for .NET
Oracle Developer Tools for Visual Studio