The If you ever even get close, you're doing it wrong :)
comment was in direct answer to the question: What is the maximum number of inner joins can a SQL query have?
.
Indeed there is a limit to this number of joins, with all (most) DBMSes, including SQL Server, but this is not a practical limit, i.e. if you approaching it, your database / query structure probably needs to be revised.
Edit: It appears that with SQL2008 this limit has been removed (or rather "pushed" to "Limited only by available resources"). In SQL2000, the limit was 256, cf "Tables per SELECT statement"
(which I think is one of the relevant limiting factors) in the following Microsoft documentation pages
I didn't find -nor look for in earnest- the SQL 2005 documentation. Also note that the SQL 2000 limit of 256 can likely be artificially boosted by introducing views (would one wish to go beyond a readily monster-ish 250+ tables query ;-) )
The query shown, in this question is quite proper syntactically and semantically, and will likely be efficient and provide the desired results; this of course depends on the specific intent and the particular indexes available (if the tables are "big").
[Stackoverflow] Point of order: typically you should try and address this kind of follow-up questions within the very original posting (unless the new question effectively discusses other concepts or issues, rather independent from the original question).