NewsGroupies

When we dev a database we are supposed to cut the data up into as many
short, narrow tables as possible, right? (I know I know there's more to
it than that...)

So I have a table with two foreign-keys into (the same) five lookup
tables, and to produce a View with both sets of looked-up values side-by
side I have two LEFT JOINs on two nested FROM (SELECT ) statements. The
five lookup tables therefore appear twice.

So I write a query that links this view to some other tables, and ISQL_w
says I blew the 16 table limit.

16 tables??

Is this a limitation of SQL Server, ISQL_w, my view, or my brain?

  --  Phlip
====== http://www.***.com/ ~tegan/home.html ======
  My web page now contains 20 pages of original comics; many many more
are on the way. Whatever you think they are like (sci fi, action,
super-hero, etc), they are not.

16 is SQL Server limit.

Other limits/behaviour that surprised me when I
first learned SQL:

o  1962 byte/row limit
o  No row level locking (page level is 2K)
o  SELECTs lock affected tables (NOLOCK, however,
    is available parameter)

Version 7.0 may help some.

CRH,

You can actualy do row level locking with SQL 6.5 but only for inserts.
Its a table option.  See sp_tableoption in Books on line eg

A.      Enable insert row lock Option for All Tables of the Current Database
EXECUTE sp_tableoption '%.%', 'insert row lock', 'true'

B.      Disable insert row lock Option for sales Table
EXECUTE sp_tableoption 'sales', 'insert row lock', 'false'

Steve Robinson MCP (SQL /NT)