[AccessD] Upsize?

Hi Jim,

I think Jürgen and my response is no.
Or at least how?

BTW I disagree with 'They tent(d) to be quicker, have greater flexibility, easier to work with'
they may be safer but...
quicker - not necessarily, especially if the execution plan needs to change from execution to execution.
Flexible - whats more flexible then building a string and running that?
Easier - 80 variable cols, 50 potential where statements...  gonna be some sproc...  what is the char limit for a sproc?

cheers

Michael M


Hi Jürgen:

Can you not use Stored Procedures and just pass parameters? They tent to be quicker, have greater flexibility, easier to work with and safer.

Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jürgen Welz
Sent: December 19, 2005 9:42 PM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Upsize?

Michael:

With variable joins, do you point somthing like a list source of search 'hits' to different queries, one query for each join, or how do you handle variable combinations of joins?  Lets say there is 1 table that may be joined to 0 to 5 other tables in various combinations, being 32 possible querydefs.  I've always constructed the SQL in code and was very satisfied with the performance.  Add another table and you're up to 64 querydefs.  
That's ugly.



Ciao
J|rgen Welz
Edmonton, Alberta
jwelz at hotmail.com





>From: "Michael Maddison" <michael at ddisolutions.com.au>
>
>  Hi J|rgen,
>
>If you go with variable parameters check out the 'With Recompile' option.
>It forces a new execution plan each time the procedure is run and 
>overcomes SQL's 'parameter sniffing' problem.
>
>cheers
>
>Michael Maddison
>
>DDI Solutions Pty Ltd
>michael at ddisolutions.com.au
>Bus: 0260400620
>Mob: 0412620497
>www.ddisolutions.com.au



--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com