Any tips on how to deal with pipeline buffer leaks that are appearing when looping round a package multiple times. Also any information on whether tweaking DefaultBufferRows / Size or threads would be helpful...
(this is all stuff that either worked or wasn't as bad in the Dec CTP.. so much for progress....)
Pipeline buffer leaks
Hot Topic
- How to iterate over a recordset?
- Cube Size Estimation formula....
- sqlcmd - view
- Exporting Tables from SQLExpress 2005 to SQLExpress 2005
- Need to create <Query> statement programmatically
- Displaying a List Horizontally
- SSEM - How do you connect to an MDF file?
- Local report pdf export
- Cube installation without VS
- ALTER TABLE MODIFY
SQL Server
- New Server Registration to External Database
- Dynamically Passing a Dataset to a Report in Reporting Services 2005
- SSIS Package OLE DB Connection Issue
- Chain transact sql scripts
- Dynamic Page Breaks
- Modify the expression to be valid
- Sql Server Log Error after upgrade
- SQL Server Date/Time & other data typesV
- Assigning properties to variables
- SqlCeRemoteDataAccess Pull issue with ConnectionString
Pipeline buffer leaks
aquaseal
Tweeking the settings won't help. The problem is a setting is being retained from one execution of the pipeline to the next and not getting reset.
My only suggestion for the near term, until the fix is in, would be to put the pipeline into a sub-package and executed it in a loop. Lame, yes. I have no other suggestions, apologies.