Using a SQL Server Agent job to start a SQL Server Integration Services Pachage step.....
In the package itself, is there a way to pick the path of the package that was started?
I want to pick up the "folder" info of where the package resided that is executing, to help build some variables.
TIA,
Doug
This works for me .
Viewing the List of Running Packages
You can view the list of packages that are currently running on the server in the Active Operations dialog box. For more information, see Active Operations Dialog Box.
For information about the other methods that you can use to view the list of running packages, see the following topics.
Transact-SQL access
To view the list of packages that are running on the server, query the view, catalog. executions (SSISDB Database) for packages that have a status of 2.
Programmatic access through the managed API
See the N: Microsoft.SqlServer.Management.IntegrationServices namespace and its classes.
Use the Active Operations dialog box to view the status of currently running Integration Services operations on the Integration Services server, such as deployment, validation, and package execution. This data is stored in the SSISDB catalog.
Open the Active Operations Dialog Box
Open SQL ServerManagement Studio.
Connect Microsoft SQL Server Database Engine In Object Explorer,
expand the Integration Services node, right-click SSISDB, and then click Active Operations.
https://msdn.microsoft.com/en-us/library/hh213131(v=sql.120).aspx
Related
I am running SSIS packages on SQL Server 2016 and am trying to log events using Dts.Events.FireInformation and Dts.Events.FireWarning. While these do show in the local IDE progress section, they are not appearing in the SSISDB Logs (e.g. R-Click on a package / Select Reports / All Execution). I also tried Dts.Log() but that didn't write either. I've used logging in the past (circa 2008R2) to the old ssis logging table. I know I can use that but would rather keep these all in oneplace.
Logging level is "Basic" which should pump out both OnInformation and OnWarning.
I did look at this post on StackOverFlow which looks like it had a viable answer; however, the link to that answer is dead.
Is this just not possible to do or am I doing something wrong?
When the packages run in Visual Studio, the Information and Warning events are logged to both the Package Results tab as well as the Output window.
That data only gets recorded into the SSISDB if the server is the one running the packages.
I am using Visual Studio 2017. I am trying to create an SSIS project that works on a database I have on a server. I have the project and solution. How do I say, use this DB as source so I can create a NEW ssis package ?
Thanks
Heather F
You can create a new connection manager at either the package or project level. More details on these and their scopes are as follows.
Package Level- When the package is open in the designer, the Connection Managers window will be docked below the Control Flow. Right-click within this area go to New Connection..., highlight the OLEDB type and press Add... On the dialog that comes up, press the New... button and enter the server name that will be connected to, the authentication type (and username/password for SQL Server authentication) and the database to connect to. This database will be the initial catalog that any SQL statements will be sent to, unless they use a three part object name with the database (i.e. Database.Schema.Table). Verify the connection is successful through the Test Connection button. This connection manager is only available to the package that it is created in.
Project Level- In the Solution Explorer (if you don't see this, go to View on the top menu, then Solution Explorer), right-click the Connection Managers folder and select New Connection Manager. You can also do this from the Project drop-down on the top menu and choosing the same option. From here, you will follow the same steps as with the package level connection manager, beginning with selecting the OLEDB provider type. This connection manager will be available to all packages within the project it was created in.
Go in the Connection Managers pane and create a new connection, specific to your database type.
Then you can convert the connection to be a Project Connection(by right clicking on it).
Will my package run successfully by using SQL Server Agent if I have data viewers enabled and breakpoint? I'm using SQL Server 2008 - SSIS.
Breakpoints and Data Viewers are only artifacts that have meaning within the debugger. If running your package from SQL Agent fails, then there's a whole host of things that could be wrong, generally permission related, but a data viewer or a breakpoint will not be one of them.
No. Breakpoints and data viewers will not be a hinderance. Your package should run successfully if there are no other errors.
In This Scenario ,Answer is NO.
When create a breakpoints then we have to press next of F5 for proceed the package .
In case of data viewer there is prompt for check OK so ultimately job get failed .
I'm trying to use team foundation server power tools to add project reports to an existing team foundation server 2010 install. Here's the command I'm running with the output...
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC>
tfpt addprojectreports /c ollection:https://SERVERNAME:8080/tfs/Projects /teamproject:SANDBOX / processtemplate:"MSF for CMMI Process Improvement v5.0" /validate
The project collection does not have reporting configured. Therefore,
reports cannot be added to projects in the collection.
The error message seems to indicate that reporting services has not been set up for the whole project collection. If I log into the TFS server and run the TFS admin console, hit Reporting under the application tier, each area (warehouse, analysis services and report server) indicate that everything is configured and enabled.
Also, if I point a browser to the report server configured within the admin console I get a directory listing with two data sources listed (Tfs2010OlapReportDS, Tfs2010ReportDS) and a directory called TfsReports. In the TfsReports dir there is a Projects directory and further a directory within the projects directory which contains what I'm assuming are the default reports for a project. If I drill all the way down to an actual report Build -> Build Summary, it runs just fine.
So, it seems like reports are configured for one of the team projects, but I'm not sure how this was accomplished since I'm not able to do this for other projects. If I run the previous command and use the name of the project that already has reports for it, I get the same error message.
I don't think I have the collection URL incorrect because if I totally fudge this I get a TF31002 error indicating unable to connect to TFS.
Any thoughts? Thanks a lot.
In the TFS Administration console, go to the project collection and in the Reports Folder tab ensure that you have set the Default Folder Location.
If the tab isn't showing (because you haven't closed the admin console since you configured reporting), click the refresh button at the top of the window and it should appear.
I've deployed a SSIS package to my SQL server.
I can run the package fine by connecting to Integration Services in SSMS and right clicking on it and choosing "Run Package"
However, if I schedule the package, it fails.
It tells me to check the logs for information on why, but there is nothing in there...
Any ideas?
(this is my first SSIS package by the way)
I would guess your package is doing something the SQl Server agent deosn't have the rights to do. Often it turns out that the location of file to be imported or the location where the file exported are in directories that are not open to the account that runs the SQL Server Agent.
I also agree woth Raj who said you really need to implement logging. You can;t expect to know why something fails six months down the road if you aren't recording the details of waht is happening with the package. SSIS pacakages can be hard to debug anyway, so you need those logs to know where to start looking.
You have to implement logging to get the details of the error.
In SQL Server Agent, create a new job, configure it to execute the package and under the logging tab, start logging.
Then run the package and you can read the log in the job history.
When you said you have scheduled a job, I assume you used SQL agent. In that case you can right click job and click View History and you can see the error related to job not to the package. For detail error you need to configure logging.