General Network Error, Check ur network documentation

Hi All,
I have been facing this error since last week.
The querry is fired on the dev. server itself, so this is not a network
issue I suppose. Secondly, it's not constant, when retried the same querry
works fine.
There are no recent hotfixes, or service packs applied.
Server is a Win 2000 server, with Sql 2000 Enterprise edition , Sp 3
Any clues ?Hi
There was problems like this with virus checkers and named pipes. You may
want to check the client network utility to make sure that you are using
shared memory.
Also you may want to update MDAC or make sure it is consistent and check
disc space.
John
"k_s" wrote:

> Hi All,
> I have been facing this error since last week.
> The querry is fired on the dev. server itself, so this is not a network
> issue I suppose. Secondly, it's not constant, when retried the same querry
> works fine.
> There are no recent hotfixes, or service packs applied.
> Server is a Win 2000 server, with Sql 2000 Enterprise edition , Sp 3
> Any clues ?
>

General Network Error, Check ur network documentation

Hi All,
I have been facing this error since last week.
The querry is fired on the dev. server itself, so this is not a network
issue I suppose. Secondly, it's not constant, when retried the same querry
works fine.
There are no recent hotfixes, or service packs applied.
Server is a Win 2000 server, with Sql 2000 Enterprise edition , Sp 3
Any clues ?
Hi
There was problems like this with virus checkers and named pipes. You may
want to check the client network utility to make sure that you are using
shared memory.
Also you may want to update MDAC or make sure it is consistent and check
disc space.
John
"k_s" wrote:

> Hi All,
> I have been facing this error since last week.
> The querry is fired on the dev. server itself, so this is not a network
> issue I suppose. Secondly, it's not constant, when retried the same querry
> works fine.
> There are no recent hotfixes, or service packs applied.
> Server is a Win 2000 server, with Sql 2000 Enterprise edition , Sp 3
> Any clues ?
>

General Network Error, Check ur network documentation

Hi All,
I have been facing this error since last week.
The querry is fired on the dev. server itself, so this is not a network
issue I suppose. Secondly, it's not constant, when retried the same querry
works fine.
There are no recent hotfixes, or service packs applied.
Server is a Win 2000 server, with Sql 2000 Enterprise edition , Sp 3
Any clues ?Hi
There was problems like this with virus checkers and named pipes. You may
want to check the client network utility to make sure that you are using
shared memory.
Also you may want to update MDAC or make sure it is consistent and check
disc space.
John
"k_s" wrote:
> Hi All,
> I have been facing this error since last week.
> The querry is fired on the dev. server itself, so this is not a network
> issue I suppose. Secondly, it's not constant, when retried the same querry
> works fine.
> There are no recent hotfixes, or service packs applied.
> Server is a Win 2000 server, with Sql 2000 Enterprise edition , Sp 3
> Any clues ?
>

Function vs. Sub-Query

When my sproc selects a function (which in itself has a select statement to gather data) it takes substantially longer time (minutes) than if I replace the function with a sub query in the sproc (split second). What is the reason for this?
BjornI've seen this too. In my case when I looked at the execution plan and the server trace it appears the udf is called for each row returned where the sub query doesn't. I was using a udf to calculate the status of the records. I ended up using a view instead to calculate the status and joined my original query to the view. This is similiar to a sub query and much much faster than the udf.|||Thanks! It makes sense. It seems that the sub query runs first and only once in an sproc, extracting all the data needed for the main query.

Bjorn