I am currently working in a local environment (Both my SQL Server and Visual Studio instance is on the same laptop
I have built a SSIS package that takes data from Oracle and loads data onto a SQL Server
The package executes properly through Visual Studio 2019, but will not allow me to publish to SQL Server
I get the following error
Failed to deploy the project. Fix the problems and try again
later.:Unable to create the type with the name 'ORACLE'.
Any ideas?
I could resolve the same issue by modifying the Project Configuration Properties which I usually forget whenever I create a new solution.
Since we run SQL Server 2014 I had to align the TargetServerVersion:
Project Property Page
Related
I have several SSIS packages created some time ago which read data from one instance of SQL Server and load them to another SQL Server instance, connections have always been OLEDB and has been working fine up until earlier today when I opened one of the packages and all the OLEDB connections are now failing with an error saying 'Unable to create the type with the name 'DTS.ConnectionManagerOleDb.7'.
If I try and create a new OLEDB connection I get the 'object reference not set to an instance of an object' error'.
Have been using Visual Studio Professional 2017 15.9.37 and SSIS 15.0.2000.150, also tried with VS 2019 Community and getting the same error.
I've tried creating a new project and package and get the same error when creating an OLEDB connection manager.
Anyone with any idea what is going on? Was working on one of these packages this morning and it was working fine, since this afternoon it's buggered.
You should do these things:
Keep the Current VS Enterprise (5.7.1)
Uninstall only your SSDT through VS Installer
Current VS Enterprise (5.7.1) with PRIOR SSDT (5.5.2) (You have to install this version to resolve your issue)
enter link description here
'ssisssdt-existing-connection-strings-unable-to-cre'
I want to move my SSIS package to a new SQL Server. To accomplish that I installed MS SSDT for VS 2017 successfully on my dev laptop. I opened the SSIS project (which worked fine in VS 2015 on my old dev laptop). I opened the package and went to the file menu hoping to fine 'save a copy of' but it is missing.
It appears 'save as' is not the way to do it anymore. You need to right click the package and select 'deploy', but before I could do that I had to install and reconfigure the environment because my packages hadn't been migrated from sql2014 to sql2016 AND my visual studio 2017 didn't have ssis package support installed and configured. see unsupported below
then you have to convert the deployment model
then right click the package and save to ssis package on sql 2016. but it didn't work because I hadn't condigured ssis on sql server
create a ssis db on sql server
now you can deploy the package
And that will work if your package doesn't use project variables. but if you use variables and converted to project deployment (like I did) then you need to deploy a bit differently because your individual package wont deploy with the project level variables. In this case, You need to click the 'project' item on the menu bar and then click 'deploy' from the DDL. This will deploy all your packages and project variables at once, which is nice. This means that my dtsconfig xml configuration file is no longer in the loop, i.e., its been replaced by the project params. Its also nice because you don't need to manually create the ssis db on sql server, i.e., the project-deploy creates it for you .
I have a Database Project in Visual Studio 2013 which I use to create a dacpac file and deploy it on SQL Servers using SQL Server Management Studio. I can successfully deploy the dacpac on SQL Server 2012 but when I try to deploy it on SQL Server 2008 R2, I get the following error message when selecting the DAC package:
<DacType xmlns='http://schemas.microsoft.com/sqlserver/dac/Serialization/2012/02'> was not expected. (es3ttafd)
I have selected "SQL Server 2008" as Target Platform under Project Settings but this does not seem to modify the namespace. When I unpack the dacpac, I can see that this namespace exists inside DacMetadata.xml, model.xml and Origin.xml files.
Is there anything I can do to stop including that namespace in the dacpac (or change it to the correct one?) in order to allow me to deploy it on an SQL Server 2008? I can successfully publish the project through VS on the SQL Server but I want to be able to create a dac package and deploy it on other servers as well, using the wizard.
Thanks.
I suspect that you're using an old version of SQL Server Management Studio to deploy to SQL Server 2008. I'd suggest downloading the latest SSMS (available here: https://msdn.microsoft.com/en-us/library/mt238290.aspx) and using that to publish.
Alternately, the most recent version of the Data-Tier Application Framework (available here: https://www.microsoft.com/en-us/download/details.aspx?id=53876) includes SqlPackage.exe, which can be used to publish a dacpac file, like so:
SqlPackage.exe /a:publish /tcs:"Data Source=SERVER;Initial Catalog=DBNAME;Integrated Security=true" /sf:C:\project\mydb.dacpac
See documentation for SqlPackage.exe here: https://msdn.microsoft.com/en-us/library/hh550080(v=vs.103).aspx
I have a project that uses EF 5 (code first) in Visual Studio 2012. When I build the database it works, but it isn't showing up in the SQL Explorer for some reason. I checked the connection object at runtime and I can see that the name of the local database is not listed in the SQL explorer. What's odd is that this project doesn't have this problem on another machine. The project is under source control
Check to see if you have a running copy of Sql Server running.
I experienced the same thing; creating a project and then EntityFramework objects, and then running the project. VS 2012 created the database in my 2008 R2 db which was running at the time, but I hadn't opened it in VS, so didn't see the new db. It wasn't until I specifically opened that db in VS that it appeared.
I try to generate a Code Map for my solution but it blows up saying: Unable to connect to the specified database.
Specifically, it's trying to connect to (LocalDB)\v11.0
Why does it blow up and why does it need to connect to a DB?
Somehow LocalDb was not installed - typically it gets installed with VS 2012. So I installed SQL Server Data Tools for VS2012, which also installed LocalDb
Visual Studio uses a code index database to help store and create the code maps.