Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 255
  • Last Modified:

Unable To Parse Query

I get the results i'm looking for but still recive this error before it completes
Why?

SELECT     dbo.Segment.ROADJUR, dbo.Segment.L_F_ADD, dbo.Segment.L_T_ADD, dbo.Segment.R_F_ADD, dbo.Segment.R_T_ADD, 
                      dbo.Segment.Geometry,
                      (SELECT LTRIM(RTRIM(UPPER(ISNULL(dbo.Street.Prefix_Full, '')))) + ' ' + 
                          (RTRIM(UPPER(ISNULL(dbo.Street.Street_Name, ''))))   + ' ' + 
                          (RTRIM (UPPER(ISNULL(dbo.Street.Suffix_Cnty, '')))) + '' +
						  (RTRIM (UPPER(ISNULL(dbo.Street.Suffix_Bell, '')))) + ' ' +
						  (RTRIM (UPPER(ISNULL(dbo.Street.Suffix_Direction, ''))))) AS Name,						  
                       (SELECT     Ward_Name
                            FROM          dbo.Ward AS W
                            WHERE      (Ward_ID = dbo.Segment.Left_Mun_ID)) AS L_MUNAME,
                       (SELECT     Ward_Name
                            FROM          dbo.Ward AS W
                            WHERE      (Ward_ID = dbo.Segment.Right_Mun_ID)) AS R_MUNAME, 
					CASE WHEN dbo.Segment.ROADJUR = 'KINGS' THEN 9 WHEN dbo.Segment.ROADJUR = 'CNTY' THEN 15 
					WHEN dbo.Segment.ROADJUR = 'TWP' THEN 16 WHEN dbo.Segment.ROADJUR = 'PRIV' THEN 17 END AS LEVEL
		FROM dbo.Segment INNER JOIN
                      dbo.Ward ON dbo.Segment.Left_Mun_ID = dbo.Ward.Ward_ID AND dbo.Segment.Right_Mun_ID = dbo.Ward.Ward_ID
                     INNER JOIN dbo.Street ON dbo.Segment.Street_ID = dbo.Street.Street_ID

Open in new window

0
PtboGiser
Asked:
PtboGiser
  • 5
  • 3
2 Solutions
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
in the GUI / query designer?
if yes, this comes, I think, from the subqueries and/or CASE statements.
it might also be reserved keywords, for example "level" or "Geometry" might require to be written like [LEVEL] and [Geometry]
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
you might also start using aliases to make your query easier to read:
http://www.experts-exchange.com/Database/Miscellaneous/A_11135-Why-should-I-use-aliases-in-my-queries.html

if the above does not help, try to use a normal query window to run the query.
if that works, it's definitively a limitation of the query designer window.
if there it still does not work, comment out parts of the query until it works, and then you can concentrate on the part that is indeed raising the issue
0
 
Aneesh RetnakaranDatabase AdministratorCommented:
also try this
SELECT     dbo.Segment.ROADJUR, dbo.Segment.L_F_ADD, dbo.Segment.L_T_ADD, dbo.Segment.R_F_ADD, dbo.Segment.R_T_ADD, 
		dbo.Segment.Geometry,
		(SELECT LTRIM(RTRIM(UPPER(ISNULL(dbo.Street.Prefix_Full, '')))) + ' ' + 
		  (RTRIM(UPPER(ISNULL(dbo.Street.Street_Name, ''))))   + ' ' + 
		  (RTRIM (UPPER(ISNULL(dbo.Street.Suffix_Cnty, '')))) + '' +
		  (RTRIM (UPPER(ISNULL(dbo.Street.Suffix_Bell, '')))) + ' ' +
		  (RTRIM (UPPER(ISNULL(dbo.Street.Suffix_Direction, ''))))) AS Name,						  
		 w1.Ward_Name AS L_MUNAME,
		 w2.Ward_Name AS R_MUNAME, 
		CASE WHEN dbo.Segment.ROADJUR = 'KINGS' THEN 9 WHEN dbo.Segment.ROADJUR = 'CNTY' THEN 15 
WHEN dbo.Segment.ROADJUR = 'TWP' THEN 16 WHEN dbo.Segment.ROADJUR = 'PRIV' THEN 17 END AS [LEVEL]
FROM dbo.Segment 
LEFT JOIN dbo.Ward w1 ON  dbo.Segment.Left_Mun_ID = w1.Ward_ID 
LEFT JOIN dbo.ward w1 ON dbo.Segment.Right_Mun_ID = w2.Ward_ID 
INNER JOIN dbo.Street ON dbo.Segment.Street_ID = dbo.Street.Street_ID

Open in new window

0
A proven path to a career in data science

At Springboard, we know how to get you a job in data science. With Springboard’s Data Science Career Track, you’ll master data science  with a curriculum built by industry experts. You’ll work on real projects, and get 1-on-1 mentorship from a data scientist.

 
PtboGiserAuthor Commented:
Does not like the word Level
Thanks again
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
then use .[Level], and it should work
0
 
PtboGiserAuthor Commented:
A Wealth of knowledge as usual
Thanks guys

Is there a Huge advantage in using the
LEFT JOIN dbo.Ward w1 ON  dbo.Segment.Left_Mun_ID = w1.Ward_ID
LEFT JOIN dbo.ward w1 ON dbo.Segment.Right_Mun_ID = w2.Ward_ID

Compared to
Inner Join  dbo.Ward ON dbo.Segment.Left_Mun_ID = dbo.Ward.Ward_ID AND dbo.Segment.Right_Mun_ID = dbo.Ward.Ward_ID

Thanks
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
the 2 joins will make sure it will work, with 1 single join to "ward" you won't get any results UNLESS left_Mun_ID = Right_Mun_ID
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
thanks for the points :)
this one hence pushes me across the 38M points barrier  :)
0
 
PtboGiserAuthor Commented:
thanks i will be sure to continue to use the joins that way,
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

A proven path to a career in data science

At Springboard, we know how to get you a job in data science. With Springboard’s Data Science Career Track, you’ll master data science  with a curriculum built by industry experts. You’ll work on real projects, and get 1-on-1 mentorship from a data scientist.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now