Below link is shared by my colleague on SSIS data profiling …
Posts Tagged ‘SSIS’
Returning full error details from SQL Server Agent jobs – Link
Posted: January 5, 2012 in SSISTags: Error Handling, msdb, SQL Server Agent, SSIS
http://www.sqlservercentral.com/articles/SQL+Server+Agent/67726/
Key Take Aways –
select * from dbo.sysjobs — All the jobs in the Server instance
select * from dbo.sysjobsteps — All the steps for the jobs
select * from dbo.Sysjobactivity — The current status of each job. This is particularly useful for seeing if a job is running, or when it last ran.
select * from dbo.sysjobhistory — The history of each job when it ran, including all job steps, until truncated (this is what you see in the Log File viewer)
select * from dbo.sysjobstepslogs — The job step log for certain jobs.
— View History on SQL Agent Job show max 1KB error message from Message column of sysjobhistory table but the sysjobstepslogs table can have 2Bn characters of log info from log column
— run_status = 0 means job step is failed
*SP code to get error message for a job step
SSIS Data Sources + Configurations – Links
Posted: October 3, 2011 in SSISTags: SSIS, SSIS Configuration, SSIS Datasources
http://msdn.microsoft.com/en-us/library/cc671619.aspx
PacMan – The SQL Server Integration Services Package Manager is a utility designed to permit batch operations on arbitrary sets of SSIS packages. Users can select a single package, a Visual Studio project or solution or a file system folder tree and then validate or update all selected packages in one operation.
BIDS 2005 – SQL Server 2005 Express Edition
Posted: September 4, 2011 in SQLServer, SSISTags: SQLServer, SSIS
BIDS is only provided with the (not free) Standard, Enterprise and Developer Editions
SQL Server 2005 Express Edition does not include SSIS or the Business Intelligence Development Studio.
To get BIDS on SQL Server Express Edition use – SQL Server 2005 Express Edition Toolkit
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=19413
4 Ways to run SSIS packages outside visual studio
- Using SQL Server Management Studio
- SQL Server Agent job to schedule package to execute one time or timely manner
- Commandline excute package utility (dtexec /f mypackage.dtsx)
- Graphical execute package utility