Tips to improve performance in SQL server and ODBC.

[Florence_USA]

I am working on project of Visual Studio 2010. I have created the data base and trying to connect the SQL database to the Visual Studio 2010. But the thing is that I am something wrong because the performance of my software is very low. I think the problem is because of database design or may be because of the way I have used for linking. So I need the tips for improving the performance of SQL server and ODBC.

[Itronix]

1. You are using the Visual Studio for designing the software that means you going to connect to the table in SQL server. It will be better if you link the SQL database table permanently. This will help in opening the table in much faster way.
2. Try to minimize the server traffic and you can do this by selecting only those fields that are required. It will be better if you use “WHERE” clause in your query.

[SpearMan]

I will suggest you to use the Dynasets instead of Snapshot when you are dealing with the large recordset, because of the simple reasons given below.
1. If you use Snapshot recordset then it will load the whole data before displaying but if you use the Dynaset recordset then it will display the data as soon as the first 20 records are available.
2. If you are using the Snapshot recordset then there is risk of “out of disk space” on the local machine, because it may happen that the whole data has much larger size then the space available on the local computer.

[XDRoX]

For the better performance do not force local query processing like
1. Join operations base queries that have the keywords like “DISTINCT” or the “GROUP BY” clause.
2. Outer joins which contains the syntax that are not directly have a support of the remote database server
3. Use of “LIKE” operator with text or memo fields.