By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
429,335 Members | 2,718 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 429,335 IT Pros & Developers. It's quick & easy.

Check Linked Table Connection

P: n/a
I have a A2K database that includes some linked tables (these links are SQL
views).
Sometimes there are "issues" with the SQL server and the users receive a
timeout error whenever they try to access those records. The timeout error
occurs after 60 seconds. Many times the user has given up and used
ctrl-alt-del to end task thinking their computer has locked up.

I suppose I could change the default timeout from 60 seconds down to 30
seconds or 15 seconds. But the users would still receive a timout error msg
that isn't very user friendly.

Is their a way I can "test" the connection ->through code<- without just
accessing the records, such that if there is a problem I can notify the user
with a msgbox that tells them to contact their IT people because there is an
"issue" with the SQL server?

Thanks,
Fred Zuckerman


Mar 20 '07 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Fred,

Try to find the root cause of the timeouts. Check for proper indexes,
blocking etc. SQL Server shouldn't be having "issues".

-- Bill

"Fred Zuckerman" <Zu********@sbcglobal.netwrote in message
news:hC*****************@newssvr13.news.prodigy.ne t...
>I have a A2K database that includes some linked tables (these links are SQL
views).
Sometimes there are "issues" with the SQL server and the users receive a
timeout error whenever they try to access those records. The timeout error
occurs after 60 seconds. Many times the user has given up and used
ctrl-alt-del to end task thinking their computer has locked up.

I suppose I could change the default timeout from 60 seconds down to 30
seconds or 15 seconds. But the users would still receive a timout error
msg
that isn't very user friendly.

Is their a way I can "test" the connection ->through code<- without just
accessing the records, such that if there is a problem I can notify the
user
with a msgbox that tells them to contact their IT people because there is
an
"issue" with the SQL server?

Thanks,
Fred Zuckerman


Mar 20 '07 #2

P: n/a

Have you eliminated network congestion (not including internet if that
applies), bandwith, server resources as the fault?

Mar 20 '07 #3

P: n/a
alterego & storrboy,
Thanks, but I don't have any direct access to their SQL Server nor their
network configuration. I am an outside programmer that end-users contract,
outside of their IT dept, to create simple A2K databases. I know that the IT
dept sometimes has these SQL "issues", although I cannot determine whether
they "should" or "shouldn't". I strongly suspect they "DO" have either
bandwith or resource problems, but I cannot help them with those issues. I'm
only trying to be supportive of the end-users. I 'd like for my application
to somehow test the linked connection when the startup form loads. Then I
can immediately provide a warning message that the app will not operate
correctly until the SQL issue is resolved. This way I can prevent the
end-user from getting further into the application only to have it time-out
on some query that uses the linked data.
Fred

"Fred Zuckerman" wrote in message:
I have a A2K database that includes some linked tables (these links are SQL
views).
Sometimes there are "issues" with the SQL server and the users receive a
timeout error whenever they try to access those records. The timeout error
occurs after 60 seconds. Many times the user has given up and used
ctrl-alt-del to end task thinking their computer has locked up.

I suppose I could change the default timeout from 60 seconds down to 30
seconds or 15 seconds. But the users would still receive a timout error
msg
that isn't very user friendly.

Is their a way I can "test" the connection ->through code<- without just
accessing the records, such that if there is a problem I can notify the
user
with a msgbox that tells them to contact their IT people because there is
an "issue" with the SQL server?

Thanks,
Fred Zuckerman
"AlterEgo" wrote in message:
Fred,
Try to find the root cause of the timeouts. Check for proper indexes,
blocking etc. SQL Server shouldn't be having "issues".
-- Bill

"storrboy" wrote in message"
Have you eliminated network congestion (not including internet if that
applies), bandwith, server resources as the fault?


Mar 20 '07 #4

P: n/a
Fred,

Yeah, its tough when you don't have enough control over the environment to
fix the problems. Unfortunately, you don't have many options that I know of.
If the query normally takes 5 seconds or 10 seconds, then you could improve
the user experience (over what it is now) by reducing the timeout as you
suggested.

You can test the connection by opening (and closing) it before the form
loads. That will only test to make sure the connection is available. By your
description, I believe your connection is fine because you would get a time
out trying to make the connection. I think you're running into some
contention issue (blocking, etc.) on the database side. The connection
itself may be fine.

What about this idea:

1. Run the query with a 20 second (or something more appropriate) timeout.
2. If it times out, prompt the user letting him/her know that the system may
be sluggish and ask if he/she wants to continue (re-qurery).
3. If yes, then re-query with a 120 second (or something more appropriate)
timeout.

-- Bill

"Fred Zuckerman" <Zu********@sbcglobal.netwrote in message
news:5X*************@newssvr25.news.prodigy.net...
alterego & storrboy,
Thanks, but I don't have any direct access to their SQL Server nor their
network configuration. I am an outside programmer that end-users contract,
outside of their IT dept, to create simple A2K databases. I know that the
IT
dept sometimes has these SQL "issues", although I cannot determine whether
they "should" or "shouldn't". I strongly suspect they "DO" have either
bandwith or resource problems, but I cannot help them with those issues.
I'm
only trying to be supportive of the end-users. I 'd like for my
application
to somehow test the linked connection when the startup form loads. Then I
can immediately provide a warning message that the app will not operate
correctly until the SQL issue is resolved. This way I can prevent the
end-user from getting further into the application only to have it
time-out
on some query that uses the linked data.
Fred

>"Fred Zuckerman" wrote in message:
I have a A2K database that includes some linked tables (these links are
SQL
views).
Sometimes there are "issues" with the SQL server and the users receive a
timeout error whenever they try to access those records. The timeout
error
occurs after 60 seconds. Many times the user has given up and used
ctrl-alt-del to end task thinking their computer has locked up.

I suppose I could change the default timeout from 60 seconds down to 30
seconds or 15 seconds. But the users would still receive a timout error
msg
that isn't very user friendly.

Is their a way I can "test" the connection ->through code<- without just
accessing the records, such that if there is a problem I can notify the
user
with a msgbox that tells them to contact their IT people because there is
an "issue" with the SQL server?

Thanks,
Fred Zuckerman

"AlterEgo" wrote in message:
>Fred,
Try to find the root cause of the timeouts. Check for proper indexes,
blocking etc. SQL Server shouldn't be having "issues".
-- Bill


"storrboy" wrote in message"
>Have you eliminated network congestion (not including internet if that
applies), bandwith, server resources as the fault?



Mar 21 '07 #5

This discussion thread is closed

Replies have been disabled for this discussion.