The DBA Blog by Tomer Lev

SQL information, scripts, tricks and more…

SSIS Logging and Performance

SSIS Logging and monitoring

  • SQL Server Integration Services includes log providers that you can use to implement logging in packages, containers, and tasks. With logging, you can capture run-time information about a package, helping you audit and troubleshoot a package every time it is run. For example, a log can capture the name of the operator who ran the package and the time the package began and finished.

When you add the log to a package, you choose the log provider and the location of the log. The log provider specifies the format for the log data: for example, a SQL Server database or text file.

MSDN link explanation you can find here:

  • Here you can find how to enable logging in the package (I have also explained Daniel how to do it):

  • Integration Services includes logging features that write log entries when run-time events occur and can also write custom messages.

Integration Services supports a diverse set of log providers, and gives you the ability to create custom log providers. The Integration Services log providers can write log entries to text files, SQL Server Profiler, SQL Server, Windows Event Log, or XML files.

Here you can find how to configure your SSIS package:

  • SQL Server Integration Services provide a set of performance counters. Among them the following few are helpful when you tune or debug your package:
  • Buffers in use
  • Flat buffers in use
  • Private buffers in use
  • Buffers spooled
  • Rows read
  • Rows written

“Buffers in use”, “Flat buffers in use” and “Private buffers in use” are useful to discover leaks. During package execution time, you will see these counters fluctuating. But once the package finishes execution, their values should return to the same value as what they were before the execution. Otherwise, buffers are leaked. In occasions like that, please contact Microsoft PSS.

“Buffers spooled” has an initial value of 0. When it goes above 0, it indicates that the engine has started memory swapping.

“Rows read” and “Rows written” show how many rows the entire Data Flow has processed. They give you an overall idea about the execution progress.

  • Here is a link for top 10 SSIS best practices:

  • Here is some code you can use in order to store the logging to Audit table:

PackageName VARCHAR(100) NOT NULL,
ElapsedTime INT,
Status VARCHAR(100));

CREATE PROCEDURE dbo.sp_dts_addlogentry @event sysname,
@computer nvarchar(128),
@operator nvarchar(128),
@source nvarchar(1024),
@sourceid uniqueidentifier,
@executionid uniqueidentifier,
@starttime datetime,
@endtime datetime,
@datacode int,
@databytes image,
@message nvarchar(2048)
INSERT INTO sysdtslog90 (event, computer, operator, source, sourceid, executionid, starttime, endtime, datacode, databytes, message)
VALUES (@event, @computer, @operator, @source, @sourceid, @executionid, @starttime, @endtime, @datacode, @databytes, @message);

INSERT INTO AuditPackage (PackageName, PackageGuid, ExecutionGuid, StartTime, ElapsedTime)
SELECT @source, @sourceid, @executionid, GETDATE(), 0
WHERE (@event = ‘PackageStart’);

UPDATE AuditPackage
SET EndTime = GETDATE(),
ElapsedTime = DATEDIFF(ms, StartTime, GETDATE()),
Status = ‘Complete’
WHERE (@event = ‘PackageEnd’
AND PackageGuid = @sourceid
AND ExecutionGuid = @executionid);

UPDATE AuditPackage
SET Status = ‘Error’
WHERE (@event = ‘OnError’
AND PackageGuid = @sourceid
AND ExecutionGuid = @executionid);

The SSIS logging gives you the ability to find bottlenecks in your SSIS package like:

  • How much time it takes to validate packages
  • Trace each step and find out how long it takes
  • Gives you a tool you can use to log valuable events of the package.

SSIS: Custom Logging Using Event Handlers

SQL Server Integration Services (SSIS) contains some really useful logging procedures but as with most things in SSIS, it is extensible. There are 2 methods of extending the logging capability of SSIS:

  • Build a custom log provider
  • Use event handlers

Look at this link in order to find out which events to capture and how to customize them:


July 8, 2009 Posted by | Administration, General, SQL SERVER, Tips | , , , , | 1 Comment

Good DBA must support his clients

It does not really important what kind of a DBA are you: applicative or infrastructure one… the one thing you will always need to do is giving support and help to your clients: a client can be a market sales man, analyst, programmer or your CTO. You need high skills of support, if you want to be a professional DBA (and more…, but this one is very important also). Your sales man will come and ask you to give him all reports on sales made yesterday, and on which hour and to slice in by community; the analyst will want a report on member’s usage and the programmer will need help in T_SQL. You must know how to help all your clients, even if they come all at once, you will need to know how to say politely to each one of them when you will be available for doing the requested work. If you will answer politely with no press – they will all say it is nice to work with you and that you look professional in your line of duty. You, from the other hand, will need to do all you have promised to your clients. A good DBA, even if he is very professional, it does not look good, if he does not know how to give service to his clients. For example, if a programmer comes to you and wants your help in writing a stored procedure, and you are very busy with other things, give him a service by telling him that you have 10 minutes for him now, and you will be happy to help him later. I saw the other example, that a programmer came to a DBA to ask him for this help, and the DBA told him he does not have the time for him and he does not do these things. The first thing this programmer did is telling his colleagues not to go to the DBA and ask for help – not just this made the DBA a “bad name”, but also the company he works in damaged, which can lead also to bad performance on servers, due to the fact the programmer will upload a stored procedure to production servers with no help from the DBA, because the DBA does not want to help – it’s a pity! And wrong!

Want to be a good DBA – you must know how to give service to your clients!

June 27, 2009 Posted by | General | , | Leave a comment

Defragmenting Indexes in SQL Server 2005

I think this may come in handy…

June 26, 2009 Posted by | General, SQL SERVER, Tips | , , | Leave a comment

50 top high CPU queries

select top 50

st.objectid, st.dbid,

— object_name(st.objectid, st.dbid), — uncomment this line if you’re using SQL 2005 SP2

total_worker_time/execution_count AS AverageCPUTime,

CASE statement_end_offset

WHEN -1 THEN st.text

ELSE SUBSTRING(st.text,statement_start_offset/2,statement_end_offset/2)

END AS StatementText


sys.dm_exec_query_stats qs CROSS APPLY sys.dm_exec_sql_text(qs.sql_handle) st


June 22, 2009 Posted by | Scripts, SQL SERVER | , , , , , , , | Leave a comment

The old argument between Programmer and DBA

Within my work experience, there is the “old argument” between DBA and programmer. The programmer does not always understands why the DBA would not give him

permissions for executions or DML operations in the DB (INSERT, UPDATE and DELETE) .

The DBA, as a data protector, tries to do his best in protecting the database, and the programmer from the other hand wants

an access to the db, as he wants to develop new stuf and writing some T_SQL with no help from the DBA. I have to say, that although the DBA does and really wants to help the

programmer, main part of his job is to protect the data and manage permissions.

I would say, that the best solution is to give the programmer a way to work in front of the DB, but on the other hand not to give the programmer a SYSADMIN role 🙂

June 22, 2009 Posted by | General | , , , , | Leave a comment


Some DBA’s need to save the execution plan in graphic way. In order to do so you need to: your exceution query XML as filename.SQLPLAN

2. open the file with management studio, which open it in a graphic way instead of XML.

June 13, 2009 Posted by | SQL SERVER, Tips | , , , | Leave a comment