16-table Limit in SQL Queries 
Author Message
 16-table Limit in SQL Queries

Glen,
   AFAIK there is no way to get past this limit of 16 tables. The 16 tables
limit is documented in SQL Server Books Online. The only alternative I can
think of is to use temporary tables for intermediate results and break up
your 16+ table query into multiple queries.
--
Regards,

Aditi [ http://www.***.com/ ]



Quote:
> Ok, here's a weird one.  Using MS SQL Server 6.0 ( and 6.5 ), I
encountered
> an error every time I try to name more than 16 tables in a query.  Is
there
> any way to increase this amount or a work around that anyone has or knows
> of?  Seems like a pretty asinine (albeit typical MicroSoft) to have an
> application that has all these enourmous capacities for dealing with data
> yet enforces a 16 table limit on queries (ridiculous).



Fri, 09 Jul 1999 03:00:00 GMT
 16-table Limit in SQL Queries

Ok, here's a weird one.  Using MS SQL Server 6.0 ( and 6.5 ), I encountered
an error every time I try to name more than 16 tables in a query.  Is there
any way to increase this amount or a work around that anyone has or knows
of?  Seems like a pretty asinine (albeit typical MicroSoft) to have an
application that has all these enourmous capacities for dealing with data
yet enforces a 16 table limit on queries (ridiculous).



Fri, 09 Jul 1999 03:00:00 GMT
 16-table Limit in SQL Queries

Quote:
>>Is there any way to increase this amount or a work around that anyone has
or knows
>> of?  

I have hit this limit before, I have found no way to increase the number of
tables that the queries, last time I checke (4.21) you could not.  The  way
that I worked around it was using temp tables within a stored procedure,
but I am sure there is other things that you can do.

Quote:
>>Seems like a pretty asinine (albeit typical MicroSoft)

Sorry, Micrsoft inherited this limitation from Sybase.

Good luck,

Rob Morrison
DataWorks Corp



Sat, 10 Jul 1999 03:00:00 GMT
 16-table Limit in SQL Queries

Quote:

> Ok, here's a weird one.  Using MS SQL Server 6.0 ( and 6.5 ), I encountered
> an error every time I try to name more than 16 tables in a query.  Is there
> any way to increase this amount or a work around that anyone has or knows
> of?  Seems like a pretty asinine (albeit typical MicroSoft) to have an
> application that has all these enourmous capacities for dealing with data
> yet enforces a 16 table limit on queries (ridiculous).

I normally don't defend MS, but this "limitation" has been there for a
long time, since Sybase wrote the code. I believe that you also find it
in Sybase System 11.

What kind of performance do you expect from a select-statement with a
join containing let's say 25 tables? Even if you were allowed to write
it, you couldn't use it since it would run forever...

Some SERIOUS limitations are the pagelocking algorithm, varchars of max
255 chars and rows limited to 1962 bytes. These limitations does make it
a faster product, but are sometimes very annoying. And even if row size
is limited, why can't a varchar be <= (maxRowSize - sizeOfOtherColumns)?

Other limitations are the lack of before-triggers, and the ODBC server's
inability to handle more than one active statement per connection unless
the statement is a server-side cursor.

- Bj?rn



Sat, 10 Jul 1999 03:00:00 GMT
 16-table Limit in SQL Queries

... and let's not forget about the claim that you don't need row level
locking if you know your schema well enough.  :)  This limitation has
caused me to abandon locking anything but a very very small transaction.
--
Michael Yocca Database Analyst PPG Industries, Inc., Pittsburgh, PA

President PGH SQL Server Users Group
http://users.sgi.net/~myocca/sql/pghssug
Why is it that they call the place you drive your car a parkway but, they
call the place that you park cars a driveway?
disclaimer "The opinions expressed are those of the writer and not of PPG
Industries, Inc. nor any PPG-associated company."



Quote:

> > Ok, here's a weird one.  Using MS SQL Server 6.0 ( and 6.5 ), I
encountered
> > an error every time I try to name more than 16 tables in a query.  Is
there
> > any way to increase this amount or a work around that anyone has or
knows
> > of?  Seems like a pretty asinine (albeit typical MicroSoft) to have an
> > application that has all these enourmous capacities for dealing with
data
> > yet enforces a 16 table limit on queries (ridiculous).

> I normally don't defend MS, but this "limitation" has been there for a
> long time, since Sybase wrote the code. I believe that you also find it
> in Sybase System 11.

> What kind of performance do you expect from a select-statement with a
> join containing let's say 25 tables? Even if you were allowed to write
> it, you couldn't use it since it would run forever...

> Some SERIOUS limitations are the pagelocking algorithm, varchars of max
> 255 chars and rows limited to 1962 bytes. These limitations does make it
> a faster product, but are sometimes very annoying. And even if row size
> is limited, why can't a varchar be <= (maxRowSize - sizeOfOtherColumns)?

> Other limitations are the lack of before-triggers, and the ODBC server's
> inability to handle more than one active statement per connection unless
> the statement is a server-side cursor.

> - Bj?rn



Sun, 11 Jul 1999 03:00:00 GMT
 
 [ 5 post ] 

 Relevant Pages 

1. 16 Tables involved in query Limit

2. Q: Limit of 16 tables in a query

3. 16 Table limit in Query

4. 16 table limit in queries

5. 16 table limit in a query

6. Query limit of 16 tables

7. 16 Table query limit

8. Check if query exceeds 16 table limit

9. 16 tables involved in a query limit

10. sybase limit of 16 on queries /tables

11. SQL Server 6.5 and 16 Table Limit

12. SQL Server 16 table limit


 
Powered by phpBB® Forum Software