Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Sp_prepexec, sp_execute
Message
De
21/01/2003 11:50:57
 
 
À
20/01/2003 16:53:43
Information générale
Forum:
Microsoft SQL Server
Catégorie:
Stored procedures, Triggers, UDFs
Divers
Thread ID:
00743492
Message ID:
00743796
Vues:
26
I am curious cause VFP is using them, or at least causing them to be used when you set a remove view to 'precompile' and also when you use SQLCompare(). However, it looks like it is using them incorrectly or at least not the most efficient.

For example, if you set up a remote view with a parameter and set it to precomile, when you use the view then sp_prepexec is used, but when you requery instead of using sp_execute it uses sp_unprep then sp_prepexec again. Which doesn't seem right to me.

Also, when you use SQLPrePare() and then you use SQLExecute() and only having change the paremeter, once again it uses sp_prepexec. It seems to me it would use sp_execute passing the prep handle and the new parameters. It only seems to use sp_exec if you call sqlexec() again without changing the parameter.

I wanted to submit this as a bug report bug wanted to be 100% certain how they worked. The weird thing is, they aren't even in master so I can't look at the code.

BOb

>Those stored procedures are used by ODBC on the server side. I've never seen any documenation on them.
>
>Any specific reason?
>
>-Mike
>
>>Where can I find documentation on the subject SP's?
>>
>>Thanks,
>>BOb
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform