0 - 23 of 23 tags for index

I downloaded this Geospatial Shapefile:
The table that was created by loading the shapefile looks like this:

Life often requires comprises. In a data warehouse, there's often a trade-off between providing quick response times to reporting users running complex reports, and loading tables with new up-to-date data. Adding join-indexes to a table can speed up reports, and solve redistribution problems, but do come at a cost to table updates.

Hi!. I have the following query:

create multiset volatile table newTable, no log as (
SELECT so.*, pu.*
FROM db.table1 so
left outer join db.table2 pu on so.id = pu.id
) with data primary index(id) on commit preserve rows;

Which throws the following error when run:

I have recently encountered an issue where after running a COLLECT STATS statement on a table, the statistics displayed in the HELP STATS results aren't updating. I found that if I DROP STATS on the index or column and then re-collect stats, it will correctly display.

Hi Experts
I have two requirements. Need your help to solve them for project.
1. there is TableA with 10M rows and 50 cols. Need to update only 3 cols out of them for 1M rows. Will a single update query be efficient or there is a better way?

Can a column that will be encrypted be used as part of an index? 

I discovered last night from UseTheIndexLuke that if there's an index on col1 and an often-used query uses UPPER(col1), the index will not be used because UPPER(col1) is not the same as col1. So the author recommended to use UPPER(col1) if it's an used often on the table.

I'm logged in with dbc user.
I'm ALTERing a table to add Foreign Key Constraint with Following statement
ALTER TABLE testdb.Master2 ADD CONSTRAINT fk_Master1 FOREIGN KEY (Master1ID) REFERENCES testdb.Master1(Master1ID);
its works fine.
But when i write this in a procedure

Hi to the performance experts among you.
We have a pretty large key table, with at least one VARCHAR(30) column storing the real world source key, here SOURCE_KEY_COLUMN1, and one bigint column storing the surrogate key (PI), here EVENT_ID.

creating a table with item, origin, destination.
what is the best way to index the table when the user may
query by either item/origin or item/destination?



There may be a discussion already in this forum about Hash and Join Index.

Still I am creating this post because I want to clarify few queries for my own understanding.


I am creating a HASH INDEX: here the PI of the table is (emp_id)


Hi All,
I have a performance issue with a query. Below is the sample query where sales table does not have any index on cust_ky, but rep has cust_ky as a NUPI. Volume of rep is about 13 million and sales is 100 million.
select r.rep_nm, s.qty
from sales s join rep r on s.cust_ky = r.cust_ky

I used the TDDoc and searched in this forum, but didn't find anything.
Is it possible to get any information about the secondary index usage?
To explain our situation: we want to drop secondary indices which weren't used for long time. Are there any dbc-tables or other possibilities to get this info?

I'm new to Teradata and have a question on creating a table with a CPPI.
I have a table with a few hundered million rows. I want to create partitioning on a column called SAP_CODE whose structure is always four digits. The first digit is alphanumeric the last 3 digits are numeric, e.g. S001, M123, Z012.

Good Day Folks...
3 Q's bunched up on stats ...
<> When should you collect Index stats  and column stats for the component columns , both as against just Index stats. How does index stats help and how does stats on component columns that make up the Ix help 


Is there any way to partition directly on a small (ie. CHAR(3)) character column, without defining a CASE_N or RANGE_N for the column (ie. partition on all unique values of the column)?

I am relatively new to using geo functions but I want to make sure my places dimension table does not have any duplicates by doing a delta operation from the freshly geocoded records in my staging table.  First, I attempted to do a left outer join on the point_geo column:


I need to get the following information of all table indices of a table with the JDBC 'getIndexInfo()' method
to be able to create a similar table but with modified indices.

- The index number
- The index column name of the index number
- The index column position of the index number
- The unique index flag of the index number
- Primary or Secondary index flag of the index number

The first 4 are returned nicely by the 'getIndexInfo()' method.

But I'cant see any information returned by the 'getIndexInfo()' method that
looks like a 'Primary or Secondary Index' flag.

Can any one tell me what is the difference between key and index?

what is the difference between primary key and unique primary key?

Ashok Reddy Daggula

I have a table that resolves the M-M relationship between my member and postal address tables. Member table has UPI on mbr_key. Postal Address has UPI on postal_addr_key. What's the best indexing scheme for the xref? Right now it has a NUPI on mbr_key. Would a composite on mbr_key + postal_addr_key help the join to BOTH parent tables? I think probably no, but what is the best? Most queries will need all 3 tables and will be driven from the member side (wanting to find one of the addresses associated with the members identified in the member filter condition(s)).