LISA GEORGE
asked on
unable to parse query text ;
i have 3 tables from oracle db and need to create report based on them
but in query designer it's showing unable to parse query text ';'
seems one of the column in table is having ; value for the data
so how can we avoid this
select * FROM products p,
CUSTOMER c,
order s
where p.product= s.order and p.productID = c.productID;
that's the query i have used in report
i am totally new to oracle db so don't know how to combine tables and get data in dataset
kindly can some one send me link where we have information on ssrs reports using oracle db
thanks in advance
but in query designer it's showing unable to parse query text ';'
seems one of the column in table is having ; value for the data
so how can we avoid this
select * FROM products p,
CUSTOMER c,
order s
where p.product= s.order and p.productID = c.productID;
that's the query i have used in report
i am totally new to oracle db so don't know how to combine tables and get data in dataset
kindly can some one send me link where we have information on ssrs reports using oracle db
thanks in advance
ASKER
@johnsone thank you for your answer
as i can't modify anything in db tables how can i avoid that ; using query in ssrs report
kindly let me know please
or can i create view or anything in oracle db to avoid that ;
if so how can we do that
as i can't modify anything in db tables how can i avoid that ; using query in ssrs report
kindly let me know please
or can i create view or anything in oracle db to avoid that ;
if so how can we do that
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
To tools like SQL*Plus or SQL*Developer the ; is an end of statement terminator. SSRS is just passing what you give it through to Oracle and it is sending the ; as part of the query. That is where the error is coming from.
Johnsone is correct about the "select *..." syntax. That is a "lazy programmer's" approach to writing Oracle queries. Yes, it is legal Oracle syntax. But, like he said, this will usually cause a lot more network traffic than you need, since this will cause Oracle to return *ALL* columns in the tables, and you likely don't need them all in your report. Also, if a developer ever adds a column to any of these tables, the report will automatically include the new column, so the results then will be different from what that query returns now.
ASKER
thank you guys
it worked
it worked
Also, you may want to look at the ANSI join syntax
Open in new window
There is nothing wrong with your join syntax, most people just are looking for the ANSI syntax now.Also, you should not select all columns. You really should only select the ones you really need. You are going to cause an issue with multiple columns with the same name in the select and you are generating an awful lot of network traffic that you don't need.