Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
Yonkouturko
Yak Posting Veteran
59 Posts |
Posted - 2014-07-04 : 22:23:03
|
i created a vb.net system with sql server 2008 as dbaseand retrieving data is quite slow.. its locally use by not more than 20 PC clientsthe problem is retrieving the data in run time of the vb.net appits kinda slow in retrievali hope you can give some advice on my problem..any kind of response will be much appreciated!! thank you!! have a nice day!!! |
|
BBarn
Starting Member
14 Posts |
Posted - 2014-07-07 : 08:43:10
|
IndexesNumber of rows retrievedBLOBS/Multiple BLOBS per rowWidth of fetchSize of fetch (Bytes)...All of these have an impact on performance. Examine the execution plan in SSMS as well as the execution times in SQL Profiler. Look for specific queries that are slow, not all of them have to be slow, one bad one can ruin performance.Connectivity to the DB - If you are connecting through a broker or application server, is it multi-threaded? You can have great performance from one PC, but if you are not handling your connections correctly, single threading your connections can kill "network performance". I would suggest finding either the query(s) that are problematic and looking for any design bottlenecks that can be removed/reengineered for better performance. These are general guidelines, without know more details about your application I can only offer general insights...not that any of these have ever been a problem for me! ;) |
|
|
|
|
|