I have 2 streams which receive JSON objects through HTTP. I create 2 SSIS packages to PUSH json objects to Streams. I test them individually and they work fine.
Now I want them to execute simultaneously. I try to start 2 instants of SQL Server Data Tools for Visual studio 2013. But I couldn't do that.
I'm working on Windows Server 2012R2. How I can open 2 instants of SSDT for VS13? Or there is any other way to execute SSIS packages simultaneously?
Create a new package called master package. Inside that package you add 2 tasks called Execute Package Tasks. Then you reference each task to your 2 ssis packages you have created. and then you just run your master package.
Just like this then they will run simultaneously:
Related
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 an SSIS project created in VS 2017.
It is in the project model.
I have a number of tsql scripts i want to execute as part of the deployment. I cannot find anywhere in the project to add additional deployment scripts.
Is it even possible?
No it is not possible to include extraneous scripts or executables to be automatically executed when you deploy an SSIS project. They have to be executed separately.
Having created a SQL Server maintenance plan in a SQL Server 2008 R2 instance, how can I import the definitions into a Visual Studio 2013 SSDT database project?
I don't mind using pre- and post-deployment scripts if that helps but I want it to be in a database project and to be able to build the project in VS and then to be able to deploy either a new instance of the plan, or to be able to synchronize an existing plan instance with the definitions in the database project. Also, drop and re-create is entirely acceptable.
Does anyone else already know how to do that ?
First of all maintenance plans are not supported by SSDT.
You can export it manually as an xml template file and then try to write some sql/batch post deploy scripts to deploy it.
You can find general instruction here (read comments also): https://robertbigec.wordpress.com/2013/10/03/automating-deployment-of-sql-server-maintenance-plans/
One note: The exported xml template contains some specific values such as server name or path to backup/log file locations. You might want to write custom script to get these values from target machine and replace it in the xml file.
I have installed ssis file watcher task on my laptop which is running a local copy of sql server 2012 and visual studio 2010.
My question is once i have built the ssis package and wanted to run it on a different server do i also need to install the ssis file watcher addon on the server as well as my laptop??
The short answer is yes.
SSIS does not come with an in-built file watcher task, so it sounds like you installed something like this: http://www.sqlis.com/post/file-watcher-task.aspx. In order for the server to be able to execute the package it will be looking for the file watcher ell in the GAC. The task I noted here has an msi file which will take care of the installation process. If the task does not, the least that you need to do is just get the dll in the gac, it does not need to go in the sql server folders which are only necessary for development.
Does Visual Studio 2010 support managing SQL Server jobs in the Database Project?
I am working with a database project in Visual Studio 2010. I would like to manage my database scheduler job in my database project. It seems that I could not create any server object in the database project.
What we do at my company is:
Script out your jobs to be re-runnable (either drop/create or skip if exists)
Place the scripts in your Post-Deployment folder (and include the reference in your Script.PostDeployment.sql file as necessary)
No, you won't be able to do that. If you want to use Visual Studio to manage database projects you can use the database and server projects (what used to be called Data Dude).
You might also want to take a look at Red Gate SQL Connect. It works with databases and source control through Visual Studio.