|
|
|||||||||
|
|||||||||
|
|||||||||
| |
|||
| ||||||||||||||||||||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||
|
|||
|
Difference in exec. times in SQL Server and VB
Hi,
We have a situation where we are executing an SP in the database and it executes fine (in less than 1 second). When we call the SAME SP from VB in a RDO result set (we tried with different options like default options, no options etc.) it takes anywhere between 90 to 200 seconds and as a result times out quite often. Thanks for the help Raj |
|
#2
|
|||
|
|||
|
Running a stored procedure in Query Analyser is always faster than VB, since you do not have the extra ADO overhead.
If your SQL server and your app server are on different machines, the problem could be netwerk related. On the programming side, you do not need a COmmand Object for executing a stored procedure. This code works fine too: Code:
oCnn.Open "connection_string" oCnn.Execute "EXECUTE spNameStoredProcedure @param1 = " & _ intParameterName oCnn.Close Set oCnn = Nothing This should give you good respons time results. Hope this helps,
__________________
- Rogier Doekes |
![]() |
| Viewing: Dev Articles Community Forums > Programming > ASP Development > Difference in exec. times in SQL Server and VB |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|