Bug 2526 - SQL: level 3 naming
Summary: SQL: level 3 naming
Status: NEW
Alias: None
Product: SQL
Classification: Unclassified
Component: all (show other bugs)
Version: 11.27.13 (Jul2017-SP4)
Hardware: x86_64 (amd64/em64t) Linux
: High enhancement
Assignee: SQL devs
URL: http://sourceforge.net/support/tracke...
Keywords:
: 2854 3062 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-04-02 09:43 CEST by Martin Kersten
Modified: 2019-02-28 16:02 CET (History)
3 users (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Kersten cwiconfidential 2010-04-02 09:43:07 CEST
SQL supports 3-level naming. We do 2 with a warning when calling the 3-level  [[database_name '.'] correlation_name '.']column_name 
Comment 1 Pseudo user for Sourceforge import 2010-05-04 09:32:09 CEST
This bug was previously known as tracker item 2981001 at http://sourceforge.net/support/tracker.php?aid=2981001
Comment 2 Sjoerd Mullender cwiconfidential 2012-03-15 18:17:21 CET
*** Bug 2854 has been marked as a duplicate of this bug. ***
Comment 3 Sjoerd Mullender cwiconfidential 2012-03-15 18:17:59 CET
*** Bug 3062 has been marked as a duplicate of this bug. ***
Comment 4 Akhilesh 2019-02-28 15:24:17 CET
Hi Team,

We are facing performance issue while executing below queries, taking around 45 mins after creating partitions(Merge table concept) and order index.
We are using 100 CPU Cores linux machine and having sufficient memory.

Without applying Merge table concept, query just keep running and not coming out, then we are killing forcibly.

1) SELECT M_key, ID FROM "TABLE_TEST" WHERE ID IN (<50,000 UNIQUE IDS>);

2) SELECT COUNT(*) FROM "TABLE_TEST" WHERE ID IN (<50,000 UNIQUE IDS>);

Table "TABLE_TEST" having 122 million rows and 60 columns(data type INT).
We created 10 partitions using Merge table concept, and applied order index in column ID post partitions.

Column ID used in 'IN' clause is primary key.

Could you please help us in solving this issue ?

Thanks in advance.

Regards,
Akhilesh
Comment 5 Sjoerd Mullender cwiconfidential 2019-02-28 16:02:17 CET
Please open a new bug report for a new issue.  This has nothing whatsoever to do with three-level naming.