Hi, using prepared statements to create views is quite a useless excercise (sorry, dont mean it as harsh as it sounds). Prepared statments internally create stored procedures that will be eventually parameterized. View creation is nothing more than writing text into sysviews (or whatever) and is not an expensive operation. Using stored procedures to create views sounds a bit like overkill.

By the way, if you can connect to the database via perl, why do you extract the data by bcp? If you have the power of perl at hand why not using it for data extraction and immeadiate reporting (or so)? Performance is the only issue I could think of... However raw data as extracted via bcp usually requires some further munging to be useful.

In reply to Re: Perl or SQL ? by dokkeldepper
in thread Perl or SQL ? by Anonymous Monk

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.