Hi all,
Desperately hoping you can help, we run pentagon2000 on an
SQL Server, which runs fine on W2K PC's, but on XP
Workstations, when the Pentagon 2000 Software data is
being added or modified from a station, and it sends the
data to the SQL Server the status states in Task manager
as "Not Responding" while sending the data and waits for
the response from the SQL Server to continue its
processes. The issue I have is that although a delay of a
few seconds is acceptable and expected, on the XP
WStations it can be 20-30 seconds, in extreme cases even
longer. this is making the system unusable. Is there
anything obvious, or even obscure anyone knows of that
might be causing this.
Thanks
Ian
Ian Broome wrote:
> Hi all,
> Desperately hoping you can help, we run pentagon2000 on an
> SQL Server, which runs fine on W2K PC's, but on XP
> Workstations, when the Pentagon 2000 Software data is
> being added or modified from a station, and it sends the
> data to the SQL Server the status states in Task manager
> as "Not Responding" while sending the data and waits for
> the response from the SQL Server to continue its
> processes. The issue I have is that although a delay of a
> few seconds is acceptable and expected, on the XP
> WStations it can be 20-30 seconds, in extreme cases even
> longer. this is making the system unusable. Is there
> anything obvious, or even obscure anyone knows of that
> might be causing this.
> Thanks
> Ian
What network library are you using to connect to SQL Server? If TCP/IP
try using the IP address instead of the server name. Or try setting up a
Connection Alias on the client for both named pipes and TCP/IP and see
if that makes a difference.
Also, make sure you have the correct MDAC installed on the WinXP
clients.
The "Not Responding" does not mean the application has necessarily
stopped responding. It could either be waiting for a response from SQL
Server as you mentioned or it could be so busy processing, it won't let
the OS know that that it is alive.
Have you tried running some queries from Query Analyzer from an XP
client to see if the response you get (Select the Show Client Statistics
option) is the same as a Win 2K client.
David G.
|||[vbcol=seagreen]
>--Original Message--
>Ian Broome wrote:
an[vbcol=seagreen]
a
>What network library are you using to connect to SQL
Server? If TCP/IP
>try using the IP address instead of the server name. Or
try setting up a
>Connection Alias on the client for both named pipes and
TCP/IP and see
>if that makes a difference.
>Also, make sure you have the correct MDAC installed on
the WinXP
>clients.
>The "Not Responding" does not mean the application has
necessarily
>stopped responding. It could either be waiting for a
response from SQL
>Server as you mentioned or it could be so busy
processing, it won't let
>the OS know that that it is alive.
>Have you tried running some queries from Query Analyzer
from an XP
>client to see if the response you get (Select the Show
Client Statistics
>option) is the same as a Win 2K client.
>
>--
>David G.
>.
>
Thanks David,
Ok first off, im afraid im not SQL friendly at all, we are
a network company brought in to resolve multiple issues
which we have but this one remains. In response to your
queries:
We are using TCP/IP, with regard to using the IP rather
than the server name, im assuming you mean within the CFG
file in BDE administrator? after that you lost me im
afriad regarding connection alias.
re: the correct MDAC installed for XP, do you know what it
should be? Ive applied SP3 for SQL and SP1 for XP.
re: Query Analyzer, ive looked this up but it seems to be
a tool I have to purchase and then run queries from,
unfortunately above my head, unless you know of an
alternative way of testing this.
Thankyou for your reply, much appreciated.
Ian
|||Ian wrote:
> Thanks David,
> Ok first off, im afraid im not SQL friendly at all, we are
> a network company brought in to resolve multiple issues
> which we have but this one remains. In response to your
> queries:
> We are using TCP/IP, with regard to using the IP rather
> than the server name, im assuming you mean within the CFG
> file in BDE administrator? after that you lost me im
> afriad regarding connection alias.
> re: the correct MDAC installed for XP, do you know what it
> should be? Ive applied SP3 for SQL and SP1 for XP.
> re: Query Analyzer, ive looked this up but it seems to be
> a tool I have to purchase and then run queries from,
> unfortunately above my head, unless you know of an
> alternative way of testing this.
> Thankyou for your reply, much appreciated.
> Ian
Query Analyzer is a client tool that comes with SQL Server. There is no
charge. If you have WinXP SP1 installed, you should be fine.
It sounds like you need a DBA to do some performance testing to see
where the problem is.
David G.
Thursday, March 22, 2012
Delay with XP
Labels:
ansql,
database,
delay,
desperately,
microsoft,
mysql,
oracle,
pcs,
pentagon2000,
run,
runs,
server,
sql,
w2k,
xpworkstations
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment