harunh
February 21st, 2001, 11:46 PM
hi there,
I've a problem that has been bugging me and my colleages. The com+ application we developed is slow (select, update and insert - 7 secondsresponse time). For you information this is our setup.
Com+ component developed using VB which client running on W2K machine. The com server is COM+ and database is MS SQL server 7.0 both on W2K os (all running on local LAN). The database is fresh setup and free from doing any hardcore database activities. We connect to the SQL server via file DSN.
I cannot think of any unusual coding that can lead to the said problem. FYI we did called the SetComplete and SetAbort.
I did change the com+ server (business tier) to a machine which also host the data tier (MS SQL SERVER) and the problem is gone. It is fast. But if the com component is located on a different machine from the SQL server, the problem will persists. If we change the component to using Stored Procedure, the response time is better (but still slow about 4 seconds) but not as fast as if the com server is located in the same maching as the database. Can anyone shed some light . TIA.
I've a problem that has been bugging me and my colleages. The com+ application we developed is slow (select, update and insert - 7 secondsresponse time). For you information this is our setup.
Com+ component developed using VB which client running on W2K machine. The com server is COM+ and database is MS SQL server 7.0 both on W2K os (all running on local LAN). The database is fresh setup and free from doing any hardcore database activities. We connect to the SQL server via file DSN.
I cannot think of any unusual coding that can lead to the said problem. FYI we did called the SetComplete and SetAbort.
I did change the com+ server (business tier) to a machine which also host the data tier (MS SQL SERVER) and the problem is gone. It is fast. But if the com component is located on a different machine from the SQL server, the problem will persists. If we change the component to using Stored Procedure, the response time is better (but still slow about 4 seconds) but not as fast as if the com server is located in the same maching as the database. Can anyone shed some light . TIA.