Dropping a wrapper
There are several reasons why you might want to drop a wrapper.
Before you begin
To issue the DROP WRAPPER statement, you must have SYSADM or DBADM authority.
About this task
Sometimes there is more than one wrapper that you can use to access a data source. The one you choose might depend on the version of the data source client software that you are using. Or it might depend on the operating system that you are using on your federated server. Suppose that you want to access two Oracle tables and one Oracle view. You are using Oracle Version 10, and the operating system on your federated server is Windows. Originally you created the SQLNET wrapper. Since the Federation component does not support the SQLNET wrapper, you can drop the SQLNET wrapper and create the NET8 wrapper.
Another reason to drop a wrapper is that you no longer need access to the data source that the wrapper is associated with. For example, suppose that your organization has a requirement to access client information in both Informix® and Microsoft SQL server databases. You create one wrapper for the Informix data source and one wrapper for the Microsoft SQL Server data source. Later your organization decides to migrate all of the information from Microsoft SQL Server to Informix. You no longer need the Microsoft SQL Server wrapper and you can drop it.
- All server definitions that are dependent on the dropped wrapper are also dropped.
- All objects that are dependent on the dropped server definitions are also dropped.
- All nicknames that are dependent on the dropped server definitions
are also dropped. Dropping the nicknames dependent on the server definition
affects the objects dependent on those nicknames:
- Any index specifications dependent on the dropped nicknames are also dropped.
- Any views dependent on the dropped nicknames are marked inoperative.
- Any materialized query tables dependent on the dropped nicknames are also dropped.
- All packages and cached dynamic SQL statements dependent on the dropped nicknames are marked invalid, and remain invalid until the dependent objects are re-created.
DROP WRAPPER MSSQLODBC3