[AccessD] SQL Speed

If I were using SQL Server, I would write one sproc foreach SQL statement
and then write a wrapper sproc that calls each one of them in turn. For
testing purposes, I would probably "batch" them into several wrapper sprocs,
say each calling 1000 of the "child" sprocs, so I could get an idea what's
taking too much time, and optimize there. The outermost sproc could call the
middle sprocs that each call 1000 of the inner sprocs.

hth,
Arthur


On 8/8/07, Mark A Matte <markamatte at hotmail.com> wrote:
>
> Hello All,
>
> I am involved in a project that will be web based.  The database will
> either
> be access or SQL Server.
>
> The question is:  I need to run a bunch (maybe 10K) of SQL statements
> againts a single table...or flat file, whatever is best, containing about
> 4K
> rows.  The results of each will be appended to a second table, or emailed
> instantly (ahh...idea...good place for a JC style Class).  The SQL
> statements themselves will be stored in a table.
>
> Does anyone have any ideas/suggestions about approach?  I will need ALL of
> the SQLs to run in less than 5 minutes.  I know 1 runs in a fraction of a
> second...I just don't know what that fraction is to calculate time needed.
>
> Being there are so few rows involved...but so many SQL statements...and
> speed is an issue...will there be a signicant advantage using SQL Server
> or
> Access?
>
> I'm thinking of having the SQLs in a table and looping through and
> executing
> each...I just don't know if this is the best approach?
>
> Thanks,
>
> Mark A. Matte
>
> _________________________________________________________________
> Booking a flight? Know when to buy with airfare predictions on MSN Travel.
> http://travel.msn.com/Articles/aboutfarecast.aspx&ocid=T001MSN25A07001
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>