I was wanting to know if there was a way to run an SSIS package, besides in the IDE to monitor the progress by step.
To explain this a little better when you run a DTS package that has say 5 steps in it,the process shows you each step, which step it is currently running, which ones have fail/sucsess and so on.
Is there a way to do this with a SSIS package.
I tried running a SQL job that did 2 SSIS packages and 2 T-SQL statements but, the job just showed the job running and no details about what it was doing or what step it was on and so on.
Thanks in advance for any help you can provide on this topic.
Robin
Have you tried out Logging? Package logging should be able to give you a whole lot of information about the package such as the component run time, success/failure and etc. If you want to view it on the GUI side then I am afraid, you will have to run it in BIDS which is not optimal when you think about production environment.
Related
Does it make sense to use Apache Airflow to orchestrate/automate ETLs, and subsequently dispatch reports via SSRS or SSIS? Put another way, I'm wondering if I can wire up an Airflow DAG to SSRS or SSIS. The MsSqlOperator Airflow operator looks like it interfaces with SQL Server, but I can't find any reference to a provider for SSRS or SSIS.
This is meant a very general question, I'm looking for directional guidance, as opposed to code examples (although I'll happily take those). Just wanting to know if I am going to pursue something that isn't going to work or is otherwise a bad idea.
Assuming you're looking to orchestrate the running of a report or running of an SSIS package, yeah sure, that's doable.
SSIS
Assuming you're working with the project deployment model, a package run is a few stored procedure calls strung together
create_execution creates an instance of an execution
set_execution_parameter_value allows you to configure values for an instance of that execution
start_execution begins the actual running of the package
Depending on whether you want the package running in synchronous or asynchronous (default) mode, you might want to set the SYNCHRONIZED bit.
SSRS
I'm not sure what you're looking for here but we trigger the proc add_event to kick off a subscription which then gets emailed out but I have seen plenty of questions from people that want to run an ssis package that pulls a report and exports to csv/pdf/etc
https://businesswintelligence.com/content/26/manually-trigger-ssrs-subscription
Docs/Learn
https://learn.microsoft.com/en-us/sql/integration-services/system-stored-procedures/catalog-create-execution-ssisdb-database?view=sql-server-ver16
https://learn.microsoft.com/en-us/sql/integration-services/system-stored-procedures/catalog-set-execution-parameter-value-ssisdb-database?view=sql-server-ver16
https://learn.microsoft.com/en-us/sql/integration-services/system-stored-procedures/catalog-start-execution-ssisdb-database?view=sql-server-ver16
https://andyleonard.blog/2015/11/the-synchronized-ssis-execution-parameter/
I have an issue that is bothering me, and I was thinking maybe someone might be able to help.
The thing is, I have a project made up by multiple packages that are executed within a master package.
When i run the master package, the execution begins, but when it hits the first package that it needs to execute, it just stops.
The output shows me the following things:
SSIS package "Master_Package.dtsx" starting.
SSIS package "Master_Package.dtsx" finished: Canceled.
If i enter that package and run the data flow in it, it works perfectly, but if i run the entire master package, or i just execute that package alone within the master package page, it just stops.
Any help would be gladly appreciated.
Thank you for your time!
Calin
Silly and obvious question: Are you using the execute package task on your master package? If so, are you referencing the right child package at the correct location?
It is a straight forward call from Master to Child even if you are passing parameters within the packages and should be no reason for child package to abend unless you are not calling it correctly.
I realise this would be massively complex under the hood in SSIS.....
But is there a way to run a SSIS package in Visual Studio in a demo mode, that does not alter any data. Only runs a "simulation"?
I can imagine this would be very complex under the hood - running all sorts of transactions and rolling them back reliably.
But other microsoft tools such as MSDeploy are able to simulate (but admittedly it would be much simpler), so I'm hoping (I think I might be asking too much), that SSIS might have a similar feature
thanks for the help
There is no demo feature in SSIS. To do what you want, you'd be best to have a script that you run after the package execution to restore the database to it's original state. Or to restore a stable backup of the database.
No, there's nothing built in to SSIS that will run a package as a simulation.
I need to execute 29 ssis packages. So planning to create one master package which will execute all these packages. I don't know how to implement this. Can you please explain in brief. Thanks in Advance !
This article does a pretty good job on giving a high level summary of what a master package does, which is basically a package executing other packages in the control flow: http://dichotic.wordpress.com/2006/10/30/creating-the-master-package/
This article goes over logging, variable scope, transactions, etc. from a fairly high level : http://74.125.95.132/search?q=cache:zMWg5KkFGZcJ:dmachicago.com/WhitePapers/SSIS%2520Master%2520Control%2520Package.doc+ssis+master+package+template&cd=3&hl=en&ct=clnk&gl=us
Alternativly, just use the execute package task. You have to deploy your ssis packages to the server first for this to work.
In VB pseudocode, I'm trying to accomplish the following using SSIS (either 2008 or 2005)
If FileHasAlreadyBeenDownloaded = False Then
DownloadTheFileFromFTP
End If
ImportTheDownloadedFile
To do this in SSIS I have a script task to check for the file, and if it exists it transfers directly to the DataFlow Task using conditional expressions. If the file doesn't exist, it transfers to the FTP Task, and the FTP Task transfers to the DataFlow Task.
It seems, though, that I can't have two tasks lead into one common shared task, because no matter which path the code takes it won't execute the DataFlow Task. If I make a copy of the DataFlow task and have each path go to its own Task, then all works perfectly.
Is this a documented thing with SSMS that I just haven't found? I looked through 31 pages of questions on SSMS before posting, so hopefully this isn't a stupid question.
I also tried using Expressions on the FTP task to set "Disabled=#FileAlreadyDownloaded=True" but that works only in SSMS 2008 and didn't seem to work in SSMS 2005.
Thanks so much for any pointers on this!
It might be worth trying putting the script task and the FTP task inside a container task, and link the the container to the data flow task on success.