Dropping a wrapper

There are several reasons why you might want to drop a wrapper. For example, you might no longer need access to the data source that the wrapper is associated with.

Before you begin

Ensure that you have SYSADM or DBADM authority.

About this task

Important: There are serious consequences when you drop a wrapper. Other objects that you registered with the federated server are impacted:
  • All server definitions that are dependent on the dropped wrapper are dropped.
  • All objects depend on the dropped server definitions are dropped.
  • All nicknames that depend on the dropped server definitions are dropped. Dropping the nicknames that depend on the server definition affects the objects that depend on those nicknames:
    • Any index specifications that depend on the dropped nicknames are dropped.
    • Any views that depend on the dropped nicknames are marked inoperative.
    • Any materialized query tables that depend on the dropped nicknames are dropped.
  • All packages and cached dynamic SQL statements that depend on the dropped nicknames are marked invalid, and remain invalid until the dependent objects are re-created.

Procedure

Use one of the following methods:

  • Command line:

    Issue the DROP statement.

    Example:The following statement drops the Microsoft SQL Server MSSQLODBC3 wrapper:
    DROP WRAPPER MSSQLODBC3 
  • Web console:
    1. Click Administer > Remote Tables.
    2. Click Manage Servers.
    3. Click a wrapper name.
    4. Click Drop.