1. Data Virtualization Demoette… DDL Feature
Hello, and welcome to the Demoette series for Cisco Information Server, or CIS. Demoettes are brief instructional videos that demonstrate specific features of CIS.
In this Demoette, we discuss the DDL Feature for CIS Virtual Databases.

2. Agenda What is it and why does it matter? A basic demo Summary
Here is our agenda.
We begin by defining the DDL Feature and outlining its importance for our customers.
Next we walk through a very basic demo of the DDL Feature.
Finally, we summarize the contents of this demoette.

3. Agenda What is it and why does it matter? A basic demo Summary
Let’s begin by discussing what the DDL Feature is, and why it is important for our customers.

4. What is it?
DDL Feature
Associate a CIS Virtual Database with a physical database
Clients may then:
Query virtual resources
Execute DDL that takes place on the associated physical database
Supported on SQL Server, MySQL, Oracle, Netezza, and Teradata
DDL stands for Data Definition Language. The DDL Feature in CIS enables a CIS developer to associate a published virtual database with a physical database. CIS clients may then query virtual resources in the usual manner, but they can also execute DDL statements that will be executed on the associated physical database. Supported DDL statements include Table Create and Drop, Column specification, and Primary Key specification.
The virtual and physical databases work together to provide a seamless experience for clients. Clients execute all operations against the CIS virtual database, and the physical database is completely transparent to them.
Supported physical databases for the DDL Feature include Microsoft SQL Server, MySQL, Oracle, Netezza, and Teradata.

5. Why does it matter? DDL Feature Use of temporary tables in queries
Materialization of virtual tables
Creation of test data
The DDL Feature is important to our customers for many reasons. For example, it enables data consumers to execute queries that create temporary tables. It also helps consumers who wish to materialize virtual views in a database repository. It can also be very useful for creation of test data.

6. Agenda What is it and why does it matter? A basic demo Summary
Next, let’s walk through a very basic demo of the DDL Feature.

7. Demo: Here is the business problem…
CIS
Here is the business problem that we illustrate in this demo. A Business Analyst wants to create a point-in-time snapshot of some data available in a CIS virtual database. This data can then be accessed by a data visualization tool.
Because we do not want the data to change over time, we will use the DDL feature to create a table on the associated physical database, which in this case is MySQL. We can then populate this physical table by querying a virtual table, thus providing a point-in-time snapshot. When our analysis task is finished, we will then Drop the physical table from MySQL.

8. Before you begin: Install a Supported Database
Before you begin this demo, install or gain access to one of the database products supported by the CIS DDL Feature.

9. Demo: Set Up Resources
We are ready to begin our demo. First, create a data source that uses a physical database that supports the DDL Feature.
<CLICK> Next, publish the CompositeView resource from the Examples folder that ships with CIS.
<CLICK> Here, we create a virtual database, catalog, and schema for the published resource.

10. Demo: Set Up Resources
Now open the virtual database, and navigate to the Composite DDL tab.
<CLICK> Browse to the data source that supports the DDL Feature, and select it. This physical database is now associated with the virtual database.

11. Demo: Use the DDL Feature
Now we are ready to use the DDL Feature from an external client to CIS. Here we use Squirrel, a freeware SQL utility, to connect to the CIS virtual database.
<CLICK> On Squirrel’s SQL tab, we enter a DDL statement that creates a table, “demoette_table,” which contains three columns: OrderID, ProductID, and CompanyName.

12. Demo: Use the DDL Feature
Now let’s return to CIS Studio. When we refresh the namespace…
<CLICK> … we see that the new table appears in our physical datasource…
<CLICK> … as well as our virtual database. No reintrospection is required.
<CLICK> We can read the new table, but as expected, no rows are returned.

13. Demo: Use the DDL Feature
Now we return to Squirrel and execute a SQL INSERT that takes data from the CompositeView virtual table and inserts it into demoette_table on the associated physical data source.
<CLICK> Squirrel lets us query the data from demoette_table…
<CLICK> … and we can also query the data from CIS Studio.

14. Demo: Use the DDL Feature
Finally, let’s return to Squirrel and execute DDL to DROP demoette_table from the physical database.
<CLICK> Returning to CIS Studio, we see that demoette_table no longer appears in our virtual database.
<CLICK> It has also been removed from our data source. Again, no re-introspection is necessary; we simply need to refresh the Studio namespace.
Using the DDL feature, we have been able to create a table, populate it, and drop it. Our demo is complete.

15. Agenda What is it and why does it matter? A basic demo Summary
Let’s summarize what we have seen in this presentation.

16. Summary
DDL Feature
Associate a CIS Virtual Database with a physical database
Clients may then:
Query virtual resources
Execute DDL that takes place on the associated physical database
Supported on SQL Server, MySQL, Oracle, Netezza, and Teradata
DDL stands for Data Definition Language. The DDL Feature in CIS enables a CIS developer to associate a published virtual database with a physical database. CIS clients may then query virtual resources in the usual manner, but they can also execute DDL statements that will be executed on the associated physical database. Supported DDL statements include Table Create and Drop, Column specification, and Primary Key specification.
The virtual and physical databases work together to provide a seamless experience for clients. Clients execute all operations against the CIS virtual database, and the physical database is completely transparent to them.
Supported physical databases for the DDL Feature include Microsoft SQL Server, MySQL, Oracle, Netezza, and Teradata.
The DDL Feature is important to our customers for many reasons. For example, it enables data consumers to execute queries that create temporary tables. It also helps consumers who wish to materialize virtual views in a database repository. It can also be very useful for creation of test data.
Thank you.
Use of temporary tables in queries
Materialization of virtual tables
Creation of test data

17. TOMORROW starts here.