Archives of the TeradataForum

Message Posted: Wed, 27 Jun 2001 @ 13:56:45 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

My Archive/Recovery manual (September 2000) does include the following Usage Note relative to Views, Macros, Triggers and Stored Procedures when doing a Database COPY:

Note: Make sure you fully qualify all table, stored procedure, and view names in a macro and all table names in a view. If you do not, you may receive an error. When you execute a COPY statement, partial names are fully qualified to the default database name. In some cases, this may be the name of the old database.

For DR, we would use the same database name. But to set up a second development image we have used a number of methods built on the idea of SHOW MACRO followed by execution of the resulting CreateText. The WinDDI tool has a "COPY OBJECTS" function that does this. You could write your own application to do this. Or you can use something like BTEQ to export SHOW MACRO statements, run those and export the text, and then run the text.

	<Prev	Next>		<<First	<Prev	Next>	Last>>