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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-08-05 : 07:16:44
|
| Daryl writes "Dear SQLTeamWhen using MS Access 2000 adp's against SQL Server 2000 SP3 (and earlier) I have noticed when running a trace that sp_tables stored procedure is often invoked, needlessly, it appears. When this happens, performance is severely affected. After identifying the particular connection that runs sp_tables, and killing it, the performance of the adp is significantly improved. However, on forms with nested subforms, a new connection is sometimes spawned, and things slow down again. It seems as though the sp_tables stored procedure is used to populate the database window, and perhaps at a later stage to check permissions. We are using application role security.Is there anyway to get Access (or SQL) to avoid the unnecessary calls to sp_tables?Thanks for your help.Daryl" |
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 2003-08-06 : 11:47:09
|
| Every control, every drop down, every updateable text box on a form will open a connection...that access the database if you build forms in the traditional access manner...updateable text will open 2 connections per recordsource....I've seen consultant built stuff that opened as many as 15 connections per form....Had to rebuild the entire application...Brett8-)SELECT POST=NewId() |
 |
|
|
|
|
|
Access generates extra connections