PERFORMANCE??

[password99]

I have a Client-Server app written in PowerBuilder and using MS SQL Server MSDE 2000 engine as the database.

The connection parameters are specified in the registry and it connects using SQLOLEDB drover. The problem is PERFORMANCE.
Previously, this app was using MS Access as the DB and it worked superfast. Now that we have switched to using MS SQL Server 2000 the clients are extremely slow. If you change a field and commit it takes 2 minutes for it to come back that is unacceptable!

Is there anything I am missing? Any pointers to what I should be looking at to improve the performance are appreciated.

 

[jsteph]

I'll bet anything what you're missing is indexes. Loot at the select statements that your access forms are based on and run them through the query analyzer and see if it's doing a full table scan, which it probably is judging by the slow performance.
--jsteph

 

[password99]

The Indexes and PK are well defined and the table has 10 records only.

 

[jsteph]

If you have only 10 records and it's taking 2 minutes then something is definitely not configured correctly. I'm assuming there are *other* tables that have *more* than 10 records? If not, then Access might have been worth staying with. If so, then do you have any cascading constraint checks or integrity checks that are set up that might be hitting some larger tables? I can't see 2 minutes to update a single record in a 10 record table. Somethings missing here.
--jsteph

 

[Corran007]

Does it have any triggers on it? Other than that, i have no idea. Also, have you run updatestats to make sure sicne you ported it in?

 

[MDXer]

Try running profiler to capture exactly what is being executed on the sql server.

"Shoot Me! Shoot Me NOW!!!"
- Daffy Duck