Re: Exception.txt.dest being overwritten on multiple calls to the same package

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Allan Mitchell (allan_at_no-spam.sqldts.com)
Date: 02/26/04 

Date: Thu, 26 Feb 2004 15:31:19 -0000

What you could do is

COPY drive\folder\*.txt outputfileName.txt 

-- 
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.allisonmitchell.com - Expert SQL Server Consultancy.
www.SQLDTS.com - The site for all your DTS needs.
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"John Kotuby" <jkotuby@snet.net> wrote in message
news:evPtBUH$DHA.2664@TK2MSFTNGP09.phx.gbl...
> Thank you for your reply Alan. I had considered that option, but I was
> hoping there was a way to combine the .dest files (and .source files too)
> for each iterated package. My migration program actually consists of 10
> packages that iterate thru as many as 20 company/division records. That
> would result in 400 files to wade through to look at the exception records
> rather than just 40. I suppose I can create a final task that combines the
> similar files by name pattern, or better yet, loads them all into SQL
> Exception tables for easier inspection.
>
> Thanks again
>
> "Allan Mitchell" <allan@no-spam.sqldts.com> wrote in message
> news:efCDbWD$DHA.1212@TK2MSFTNGP12.phx.gbl...
> > Can you not programmatically do this
> >
> > So
> >
> > In each iteration you set a new value for the .ExceptionFileName
property
> of
> > the DataPump task?
> >
> >
> > -- 
> >
> > Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
> > www.allisonmitchell.com - Expert SQL Server Consultancy.
> > www.SQLDTS.com - The site for all your DTS needs.
> > I support PASS - the definitive, global community
> > for SQL Server professionals - http://www.sqlpass.org
> >
> >
> > "John Kotuby" <jkotuby@snet.net> wrote in message
> > news:Ot2mID8%23DHA.916@TK2MSFTNGP10.phx.gbl...
> > > I have a data migration package that pulls data from DBF files located
> in
> > > different folders on disk and loads the data into a single SQL table.
> The
> > > package is called from another package containing an ActiveX Script
> which
> > > sets Global Variables that tell the called package where the next DBF
> file
> > > resides.
> > >
> > > I have noticed that the Exception.txt file is appended to for each
call,
> > so
> > > that I can see the exceptions that occur for each and every DBF file.
> > > However, it appears that the associated Exception.txt.dest and
> > > Exception.txt.source files are overwritten with each call to the
> package.
> > So
> > > if I transform 6 different DBFs, only the exception rows from the last
> DBF
> > > are recorded.
> > >
> > > I can't find any setting in the graphical package designer to specify
to
> > > append rather than overwrite. Is there a Package property that I can
set
> > in
> > > code (from the calling ActiveX Script) to solve this problem.
> > >
> > > Thanks
> > >
> > >
> >
> >
>
>

Relevant Pages

  • Re: SSIS Samples set up
    ... package sample but cannot find it in the suggested directory listed below. ... you can download and install the AdventureWorks sample ... database, the Integration Services sample packages, and the Integration ... SQL Server Samples to go directly to the Microsoft SQL Server Samples and ...
    (microsoft.public.sqlserver.setup)
  • Re: Can you use osql in DTS?
    ... This sounds simple enough to do in a single package. ... ActiveX Script task to build the date and time strings to populate the ... Data Pump task that executes a proc that populates a table and then ... Columnist, SQL Server Professional ...
    (microsoft.public.sqlserver.dts)
  • Re: Can you use osql in DTS?
    ... This sounds simple enough to do in a single package. ... ActiveX Script task to build the date and time strings to populate the ... Data Pump task that executes a proc that populates a table and then ... Columnist, SQL Server Professional ...
    (microsoft.public.sqlserver.programming)
  • Re: Migrating DTS Local Package from test to production environments v7.0
    ... The version of SQL Server on which the package was create is SQL Server ... DTS runs at the client so manually will be on the invoker's PC which in this ...
    (microsoft.public.sqlserver.dts)
  • RE: Migrating DTS to Integration Services
    ... let me answer your Encryption issue when you expand your MSDB ... used to connect to your SQL Server, ... Open services.msc and restart your SQL Server Integration Service. ... Migrate DTS 2000 packages or Add Existing package (since you have migrated ...
    (microsoft.public.sqlserver.dts)