Instead of using tee, have you considered just printing directly to the file? I assume you are wanting the results to print to screen as well as to a log file. Why not do something like this:
open(FILE, ">$name") or die "Failed file open: $!\n";

my $stmt = $dbh->prepare("$sql") or die $DBI::errstr; # $sql takes 30-
+40 secs. to run
$stmt->execute() or die $DBI::errstr;

while (my @array = $stmt->fetchrow()) {
    print;
    print FILE "$_";
}
$stmt->finish();

close(FILE);

[download]
I didn't test this, but I'd bet that it's faster than running tee -- not to mention quite a bit easer to customize.
Hope that helps,
Shendal

In reply to Re: Order of output when switching filehandles by Shendal
in thread Order of output when switching filehandles by Cirollo

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.