All Forums Teradata Studio
John_Smith_00 3 posts Joined 02/16
26 Feb 2016
Newly created tables not showing in Data Source Explorer (even after refresh)

I'm using Teradata Studio 15 and it seems like all previously existing schemas and tables are loading in the Data Source Explorer just fine but I'm not able to find tables that I've recently created myself. I've tried creating the table in Teradata SQL Assistant and in Teradata Studio using both SQL and the create table button then refreshed the schema but it doesn't show up in the tables folder. I'm able to query the table (with zero records) and also if I view the database in Object Viewer the table won't show in the Tables tab but it is listed in the Space Use tab and the Type column says "Table".
 
So I can find the table in the Space Use tab but clicking or right-clicking there doesn't give any options. My goal is to load data into this table from a text file my questions are: 1) how do I get this table to show in the Data Source Explore? and 2) is it possible to launch the Data Transfer Wizard jsut by giving the data name even if it doesn't show in the explorer?
 
Thanks.

fgrimmer 553 posts Joined 04/09
03 Mar 2016

John, Is it possible that the table is being filtered out via a DSE Filter on the Tables folder? If the Tables folder is filtered, it should be annotated as [Filtered]. Or, is it a Volatile Table? Are you using caching, where you have cached that database?
Are there any error messages in the logs (.log or teradata.log)? The logs are located in your workspace directory.

John_Smith_00 3 posts Joined 02/16
09 Mar 2016

Thank you for the response, you helped point me in the right direction. I just noticed the icon for this particular database (and a few others) was different in the Data Source Explorer so I right-clicked and chose Refesh Database Cache (instead of Refresh like I had been doing previously) and I now see the tables I created. 
Is it possible, or even advisable, to turn off caching? I guess it doesn't matter as long as I know that I need to refresh the cache to find new tables, I'm just curious if there are any real impacts. 

fgrimmer 553 posts Joined 04/09
09 Mar 2016

John, The cache saves time in loading database objects into Studio's SQL Object model in that it stores the metadata on disk instead of going out to the Data Dictionary on the database server. But if the table definitions are changing frequently, caching may not be a good idea. 

You must sign in to leave a comment.