D
Dean Slindee
Within SQL Server 2005 (SP1/SP2) the ability to host .adp projects over a
SQL Server 2005 back-end was made possible.
I have converted a couple of legacy .adp projects from SQL Server 2000
back-end to a SQL Server 2005 back-end. In early A-B testing, one user,
perhaps more, is experiencing very slow response time. The user is running
both the legacy .adp project and the test .adp project on the same box
(Windows 2000 OS). I have watched as the user enters a keystroke into a
text box, and experiences 4-second delay in the echoing back of the
keystroke to the screen. On my own development PC (Vista OS), I can see a
slight slow-down, but not the echo problem.
I am wondering, firstly, whether keystrokes travel across the network and
back before appearing on the form?
Does anyone else have experiences (fast or slow) with regard to migrating
..adp projects to a SQL Server 2005 back-end?
Anyone got advise on where or what steps to proceed along to isolate the
echo problem?
Thanks in advance.
Dean Slindee
SQL Server 2005 back-end was made possible.
I have converted a couple of legacy .adp projects from SQL Server 2000
back-end to a SQL Server 2005 back-end. In early A-B testing, one user,
perhaps more, is experiencing very slow response time. The user is running
both the legacy .adp project and the test .adp project on the same box
(Windows 2000 OS). I have watched as the user enters a keystroke into a
text box, and experiences 4-second delay in the echoing back of the
keystroke to the screen. On my own development PC (Vista OS), I can see a
slight slow-down, but not the echo problem.
I am wondering, firstly, whether keystrokes travel across the network and
back before appearing on the form?
Does anyone else have experiences (fast or slow) with regard to migrating
..adp projects to a SQL Server 2005 back-end?
Anyone got advise on where or what steps to proceed along to isolate the
echo problem?
Thanks in advance.
Dean Slindee