[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2578: ------------------------------------- User has the ability to carry out this operation, it is not just tied to the restart/redeploy option. It provides a different way to update, so IMO this is OK as long as there is way to do this. On VDB import I agree. How about something like CREATE SCHEMA {name} IDENTIFIED BY DATABASE x VERSION y SCHEMA z; and mark the imported metadata as READONLY and not allow any ALTER or persistent operations. I know I worked on this, I do not think I ran through all the methods. I do not think we can have this as complete replacement with other behavior wise, especially when there is no external concept of deployment. But if want to go towards the deployment based, we can simply provide *-vdb.ddl based deployer back into this without much hassle, but we would not support ALTERS on that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)