Network Error
-
Hi,
I have a SQL Server 2000 problem I have no idea how to resolve, any assistance would be appreciated.
I have a complex full outer join query that I am running in Query Analyser for debugging purposes (original is in SP). Basically, there are two subqueries that calculate various aggregated statistical values, which are then combined into one resultset using FULL OUTER JOIN syntax.
SELECT [COLUMN_LIST]
FROM ( SELECT .... ) as c1
FULL OUTER JOIN ( SELECT ... ) as c2
ON c1.firstID = c2.firstID and c1.secondID = c2.secondID
This table joins to a couple of temporary tables that effectively define the datasets in the two subqueries. Thus these subqueries could be performing aggregate functions on between 500 and 15000 rows.
Now, when I run this on my local machine I get the following error regardless if run within the SP or Query Analyser:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData (CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
Firstly what does this error mean given that it is being run on my local database of my development machine? Could this error be indicative of data/index corruption?
Now for the killer, if I change the FULL OUTER JOIN syntax and only include a single join condition, for example:
SELECT [COLUMN_LIST]
FROM ( SELECT .... ) as c1
FULL OUTER JOIN ( SELECT ... ) as c2
ON c1.firstID = c2.firstID
Then it works fine and no errors are experienced. Could this be tempDB size/corruption issue?
I am very confused here...
Thanks,
Glenn.
-
Are there any other error messages in the SQL Error Log?
Are you generating a cartesian join when you include both join conditions? Try using SET ROWCOUNT to limit the number of rows returned and see what you get.
Another thing to try to determine if its a tempdb issue. Change your queries to use permanent tables instead.
--------------------
Colt 45 - the original point and click interface
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply