I agree that cacheing has great potential to increase performance and decrease load... UNLESS it doesn't work. Then cacheing is a liability. There is no defending a defective cache. As far as I can tell, the only way to get Teradata Studio to reflect the proper state of the DB is to close and open it. I now have that wisdom, but others will lose time. I have seen new TD clients get very mad about this behavior.
When Teradata Studio sees the words "Replace, Drop, Create" etc, it should purge the cache.
I think a great feature would be an option to disable cacheing so Teradata Studio functions more like BTEQ, where what you see is what's on the DB. No closing windows, right-clicking, etc.
Is there a way to make a feature request, or are these forums scanned?
I agree that cacheing has great potential to increase performance and decrease load... UNLESS it doesn't work. Then cacheing is a liability. There is no defending a defective cache. As far as I can tell, the only way to get Teradata Studio to reflect the proper state of the DB is to close and open it. I now have that wisdom, but others will lose time. I have seen new TD clients get very mad about this behavior.
When Teradata Studio sees the words "Replace, Drop, Create" etc, it should purge the cache.
I think a great feature would be an option to disable cacheing so Teradata Studio functions more like BTEQ, where what you see is what's on the DB. No closing windows, right-clicking, etc.
Is there a way to make a feature request, or are these forums scanned?