|
Home > Archive > MS SQL Server > August 2005 > Error: 208, Severity: 16, State: 1
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Error: 208, Severity: 16, State: 1
|
|
| ChrisR 2005-08-05, 8:23 pm |
| Ive also got lots of these errors. Dont know if this helps.
"ChrisR" <noemail@bla.com> wrote in message
news:eV%23sQagmFHA.3648@TK2MSFTNGP10.phx.gbl...
>I think Im over the long running queries thing... probably not going to
>kill my connections. I do appreciate your help, I probably just shouldnt
>have bothered to post that part and stuck to the bigger issue which is loss
>of connections. (Guess I freaked out and shoudnt have thrown that in
>there.) Any thoughts on the connections?
>
>
>
> "David Gugick" <david.gugick-nospam@quest.com> wrote in message
> news:uF0$ZNgmFHA.3300@TK2MSFTNGP15.phx.gbl...
>
>
| |
| David Gugick 2005-08-06, 8:23 pm |
| ChrisR wrote:
> Ive also got lots of these errors. Dont know if this helps.
>
You don't have to worry about many 208 errors. Many are reported for
temp table access in procedures even though the temp table is there
(it's just not there at compile time is what I think triggers it).
However, the 208 error could mean that an object that should be there is
missing. You'll need to check the statement executed just prior to the
error to see what object is being referenced.
Not sure about your lost connections. Are they just breaking randomly?
Or are statements not completing but the connection remains active?
--
David Gugick
Quest Software
www.imceda.com
www.quest.com
| |
| ChrisR 2005-08-07, 11:23 am |
| One web server will suddenly start losing connections randomly. Once
restarted, its good for maybe 20 minutes.
"David Gugick" <david.gugick-nospam@quest.com> wrote in message
news:OFoGpttmFHA.3020@TK2MSFTNGP10.phx.gbl...
> ChrisR wrote:
>
>
> You don't have to worry about many 208 errors. Many are reported for temp
> table access in procedures even though the temp table is there (it's just
> not there at compile time is what I think triggers it). However, the 208
> error could mean that an object that should be there is missing. You'll
> need to check the statement executed just prior to the error to see what
> object is being referenced.
>
> Not sure about your lost connections. Are they just breaking randomly? Or
> are statements not completing but the connection remains active?
>
>
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
| |
| ChrisR 2005-08-07, 11:23 am |
| David I just reread.... after talking to the web admin, its probably closer
to say that statements just arent completing but the connection is staying
open.
"David Gugick" <david.gugick-nospam@quest.com> wrote in message
news:OFoGpttmFHA.3020@TK2MSFTNGP10.phx.gbl...
> ChrisR wrote:
>
>
> You don't have to worry about many 208 errors. Many are reported for temp
> table access in procedures even though the temp table is there (it's just
> not there at compile time is what I think triggers it). However, the 208
> error could mean that an object that should be there is missing. You'll
> need to check the statement executed just prior to the error to see what
> object is being referenced.
>
> Not sure about your lost connections. Are they just breaking randomly? Or
> are statements not completing but the connection remains active?
>
>
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
|
|
|
|
|