Find User who dropped table in teradata DB

Login or Register for Dates, Times and to Reply

Thread Tools Search this Thread
# 1  
Find User who dropped table in teradata DB

HI Team

Is there a way to track which user dropped the table in Teradata ?
Please share the query or approach .

Login or Register for Dates, Times and to Reply

Previous Thread | Next Thread
Thread Tools Search this Thread
Search this Thread:
Advanced Search

Test Your Knowledge in Computers #415
Difficulty: Easy
HTML, CSS, and JavaScript are the three core technologies of the World Wide Web.
True or False?

7 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Records not dropped from UNIX Script

Hi All, As per my biz requirement, I need to drop the partition from our PROD table based on the retention period. Hence I have written the script and called the drop partition procedure within the script. The procedure is working fine and droped the partition from the table when I execute... (4 Replies)
Discussion started by: suresh_target
4 Replies

2. News, Links, Events and Announcements

MySQL dropped in favor of MariaDB

Fedora and openSUSE will replace MySQL with MariaDB: Oracle who? Fedora & openSUSE will replace MySQL with MariaDB | ZDNet The article also has a comment that Chakra is planning on doing the same. No doubt the Fedora based distributions are planning to do the same. (7 Replies)
Discussion started by: figaro
7 Replies

3. Ubuntu

System chrashe , dropped into Busybox

This is the mistake that i've done : First of all go to /etc/apt/sources.list folder from terminal or using file manager ... than copy the content of sources.list in to your adequate source.list. Create a file named and paste the same content In the end open the... (0 Replies)
Discussion started by: dud3
0 Replies

4. Shell Programming and Scripting

Number of processes per each user in a table

Hello guys, what i want to do is to print a table with two columns (user :: #procs) on the stdout. The first column should show the users and the second one the number of processes the respective user runs. I think I need something like the count() - function in sql, don't i? Shell: Bash ... (2 Replies)
Discussion started by: tiptop
2 Replies

5. SuSE

Recover dropped database

I have deleted a database. I restored it again with a backup. Now we lost some data of two days. Is it possible to restore this lost data? (5 Replies)
Discussion started by: Eastme
5 Replies

6. UNIX for Dummies Questions & Answers

are dropped packets a sign of network problem?

in a xen environment , i see a lot op dropped packets via netstat -i Is this a sign of network problems, or is it normal to see this kind of numbers? i'm not sure how to interprete the data. is this normal, bad, critical. What are your stats on this? I guess i have a xen issue of some sort,... (1 Reply)
Discussion started by: progressdll
1 Replies

7. UNIX for Dummies Questions & Answers

How do I find route table information

I am trying to install a new AIX server and I am migrating off of an older AIX server. Does anyone have a quick and easy method for getting the static route information from the old server so I can just maybe copy a file over to the new server ? (1 Reply)
Discussion started by: Docboyeee
1 Replies
AS(7) PostgreSQL 9.2.7 Documentation CREATE TABLE AS(7) NAME
CREATE_TABLE_AS - define a new table from the results of a query SYNOPSIS
CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE table_name [ (column_name [, ...] ) ] [ WITH ( storage_parameter [= value] [, ... ] ) | WITH OIDS | WITHOUT OIDS ] [ ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP } ] [ TABLESPACE tablespace_name ] AS query [ WITH [ NO ] DATA ] DESCRIPTION
CREATE TABLE AS creates a table and fills it with data computed by a SELECT command. The table columns have the names and data types associated with the output columns of the SELECT (except that you can override the column names by giving an explicit list of new column names). CREATE TABLE AS bears some resemblance to creating a view, but it is really quite different: it creates a new table and evaluates the query just once to fill the new table initially. The new table will not track subsequent changes to the source tables of the query. In contrast, a view re-evaluates its defining SELECT statement whenever it is queried. PARAMETERS
GLOBAL or LOCAL Ignored for compatibility. Use of these keywords is deprecated; refer to CREATE TABLE (CREATE_TABLE(7)) for details. TEMPORARY or TEMP If specified, the table is created as a temporary table. Refer to CREATE TABLE (CREATE_TABLE(7)) for details. UNLOGGED If specified, the table is created as an unlogged table. Refer to CREATE TABLE (CREATE_TABLE(7)) for details. table_name The name (optionally schema-qualified) of the table to be created. column_name The name of a column in the new table. If column names are not provided, they are taken from the output column names of the query. WITH ( storage_parameter [= value] [, ... ] ) This clause specifies optional storage parameters for the new table; see Storage Parameters for more information. The WITH clause can also include OIDS=TRUE (or just OIDS) to specify that rows of the new table should have OIDs (object identifiers) assigned to them, or OIDS=FALSE to specify that the rows should not have OIDs. See CREATE TABLE (CREATE_TABLE(7)) for more information. WITH OIDS, WITHOUT OIDS These are obsolescent syntaxes equivalent to WITH (OIDS) and WITH (OIDS=FALSE), respectively. If you wish to give both an OIDS setting and storage parameters, you must use the WITH ( ... ) syntax; see above. ON COMMIT The behavior of temporary tables at the end of a transaction block can be controlled using ON COMMIT. The three options are: PRESERVE ROWS No special action is taken at the ends of transactions. This is the default behavior. DELETE ROWS All rows in the temporary table will be deleted at the end of each transaction block. Essentially, an automatic TRUNCATE(7) is done at each commit. DROP The temporary table will be dropped at the end of the current transaction block. TABLESPACE tablespace_name The tablespace_name is the name of the tablespace in which the new table is to be created. If not specified, default_tablespace is consulted, or temp_tablespaces if the table is temporary. query A SELECT(7), TABLE, or VALUES(7) command, or an EXECUTE(7) command that runs a prepared SELECT, TABLE, or VALUES query. WITH [ NO ] DATA This clause specifies whether or not the data produced by the query should be copied into the new table. If not, only the table structure is copied. The default is to copy the data. NOTES
This command is functionally similar to SELECT INTO (SELECT_INTO(7)), but it is preferred since it is less likely to be confused with other uses of the SELECT INTO syntax. Furthermore, CREATE TABLE AS offers a superset of the functionality offered by SELECT INTO. Prior to PostgreSQL 8.0, CREATE TABLE AS always included OIDs in the table it created. As of PostgreSQL 8.0, the CREATE TABLE AS command allows the user to explicitly specify whether OIDs should be included. If the presence of OIDs is not explicitly specified, the default_with_oids configuration variable is used. As of PostgreSQL 8.1, this variable is false by default, so the default behavior is not identical to pre-8.0 releases. Applications that require OIDs in the table created by CREATE TABLE AS should explicitly specify WITH (OIDS) to ensure desired behavior. EXAMPLES
Create a new table films_recent consisting of only recent entries from the table films: CREATE TABLE films_recent AS SELECT * FROM films WHERE date_prod >= '2002-01-01'; To copy a table completely, the short form using the TABLE command can also be used: CREATE TABLE films2 AS TABLE films; Create a new temporary table films_recent, consisting of only recent entries from the table films, using a prepared statement. The new table has OIDs and will be dropped at commit: PREPARE recentfilms(date) AS SELECT * FROM films WHERE date_prod > $1; CREATE TEMP TABLE films_recent WITH (OIDS) ON COMMIT DROP AS EXECUTE recentfilms('2002-01-01'); COMPATIBILITY
CREATE TABLE AS conforms to the SQL standard. The following are nonstandard extensions: o The standard requires parentheses around the subquery clause; in PostgreSQL, these parentheses are optional. o In the standard, the WITH [ NO ] DATA clause is required; in PostgreSQL it is optional. o PostgreSQL handles temporary tables in a way rather different from the standard; see CREATE TABLE (CREATE_TABLE(7)) for details. o The WITH clause is a PostgreSQL extension; neither storage parameters nor OIDs are in the standard. o The PostgreSQL concept of tablespaces is not part of the standard. Hence, the clause TABLESPACE is an extension. SEE ALSO

Featured Tech Videos