Re: Could not allocate ancillary table for view resolution
From: Steve Kass (skass_at_drew.edu)
Date: 05/02/04
- Previous message: anonymous_at_discussions.microsoft.com: "Could not allocate ancillary table for view resolution"
- In reply to: anonymous_at_discussions.microsoft.com: "Could not allocate ancillary table for view resolution"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 02 May 2004 17:00:45 -0400
Perhaps a view definition changed, or the query plan changed because of
a change in the underlying data. Perhaps the query or the views it
refers to are more complicated than they need to be and could be
simplified. If you post the query and the related definitions of tables
and view, perhaps there will be something obvious to simplify, or it may
point to a problem elsewhere. In any case, this is a limitation of the
SQL Server engine, and if there is a query with more than 256 references
to tables, it will fail.
Steve Kass
Drew University
anonymous@discussions.microsoft.com wrote:
>>-----Original Message-----
>>I am receiving this error when running a query:
>>
>>Server: Msg 4414, Level 16, State 1, Line 1
>>Could not allocate ancillary table for view resolution.
>>The maximum number of tables in a query (256) was
>>exceeded.
>>
>>I have found the error in the knowledge base but only for
>>SQL Server 2000, we are still using SQL Server 7.0. It
>>was running fine about 3 weeks ago; I hadn't made any
>>changes to the query, and suddenly this happened. I have
>>already rebooted the server. Does anyone know where this
>>message could be coming from or how to fix it?
>>
>>Thank you,
>>Sassgirl
>>.
>>
>>
>>
- Previous message: anonymous_at_discussions.microsoft.com: "Could not allocate ancillary table for view resolution"
- In reply to: anonymous_at_discussions.microsoft.com: "Could not allocate ancillary table for view resolution"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
