Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Stored Procedures taking longer than ISQLW execution.
Message
General information
Forum:
Visual FoxPro
Category:
Client/server
Miscellaneous
Thread ID:
00007434
Message ID:
00007755
Views:
38
>1.) Have you tried SET NOCOUNT ON? It's supposed to significantly increase stored procedure execution by suppressing the message at the end of each SQL statement reporting how many rows were affected by the statement.

I'll try that, thanks.

>2.) Perhaps you've been reindexing your tables and everything without recompiling your SP? Once SPs get run, they get compiled and won't get recompiled again until a) you tell SQL Server to do so, or b) SQL Server is restarted and the SP is re-run. Only then will it take advantage of any other optimizations you've run against the table(s) it references.

No, but I've been told that before, so I'm going to keep it in mind for future use. The only indexes that change are those created from within the SP.

Thanks,
Scot.
Previous
Reply
Map
View

Click here to load this message in the networking platform