I am writing an app using MSDE for the first time.
One limitation that had been identified is that MSDE performance is reduced after 5 concurrent connections.
Looking through Tek-Tips I am reassured to see this is 5 concurrent executions, not necessarily connections and can be well managed with effective coding.
I have not come across and tips on suitable efficient coding methods that would maintain MSDE performance.
For example I have a screen with a flexgrid connected to a recordset based on a stored procedure. Everytime this grid needs to be refreshed due to record changes I had, in order to promote MSDE performance :
- opened the recordset
- redraw the grid
- close the recordset.
My understanding is that I could keep the recordset connection open without effecting MSDE performance and just refresh it as required.
Does anyone have any other thoughts.
Many thanks in advance
One limitation that had been identified is that MSDE performance is reduced after 5 concurrent connections.
Looking through Tek-Tips I am reassured to see this is 5 concurrent executions, not necessarily connections and can be well managed with effective coding.
I have not come across and tips on suitable efficient coding methods that would maintain MSDE performance.
For example I have a screen with a flexgrid connected to a recordset based on a stored procedure. Everytime this grid needs to be refreshed due to record changes I had, in order to promote MSDE performance :
- opened the recordset
- redraw the grid
- close the recordset.
My understanding is that I could keep the recordset connection open without effecting MSDE performance and just refresh it as required.
Does anyone have any other thoughts.
Many thanks in advance
