4: Exporting the Quanvert data to the new database
Note For information on working with the SQL Server Import and Export Wizard, see:
1 From the Windows Start menu, choose: Programs > Microsoft SQL Server > Microsoft SQL Server Management Studio
2 Right-click the appropriate database and select Tasks > Export Data.
This opens the first page of the SQL Server Import/Export wizard.
3 Click Next.
4 From the Data Source list, select UNICOM Intelligence DM-2 OLE DB Provider, and then click Properties.
This opens the Connection tab in the Data Link Properties dialog box.
5 From the Metadata Type list, select Intelligence Metadata Document.
6 Enter the Metadata Location, either by typing the name and location of the .mdd file or by clicking Browse. This should be the .mdd file that you created from the Quanvert database.
7 From the Case Data Type list, select Quanvert Database (read-only).
8 Enter the Case Data Location of the Quanvert database. You can either type the name and location of the Quanvert qvinfo or .pkd file into the text box or click Browse and select the file in the Open dialog box.
9 Click Test Connection.
Test connection succeeded means that you have entered all of the details correctly.
If Test connection failed is displayed, check that you have entered all of the details correctly.
10 Click OK to return to the Choose a Data Source page of the SQL Server Import/Export wizard, and then click Next.
This opens the Choose a Destination page of the SQL Server Import/Export wizard.
11 From the Destination list, select UNICOM Intelligence DM-2 OLE DB Provider, and then click Properties.
This opens the Connection tab in the Data Link Properties dialog box.
12 From the Metadata Type list, select Intelligence Metadata Document.
13 Enter the Metadata Location, either by typing the name and location of the .mdd file, or by clicking Browse. This should also be the .mdd file that you created from the Quanvert database.
14 Select Open metadata read/write.
15 From the Case Data Type list, select UNICOM Intelligence Database (MS SQL Server) (read-write).
16 Enter the Case Data Location. This should be in the form of an OLE DB connection string, for example:
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=MyDatabase;Data Source=LocalHost
17 If necessary, enter your Login ID and Password and click OK.
18 Enter the project name in the Case Data Project text box. Typically, this is the same as the database name.
19 Click Test Connection.
Test connection succeeded means that you have entered all of the details correctly and you have successfully connected to the database.
If Test connection failed is displayed, check that you have entered all of the details correctly, and, if relevant, check your network connection to the server where the database is.
20 Click OK to returns to the Choose a Destination page of the SQL Server Import/Export wizard, and then click Next.
This opens the Specify Table Copy or Query page of the SQL Server Import/Export wizard.
21 Select Copy table(s) and view(s) from the source database, and then click Next.
22 Select the VDATA table for both the Source and Destination, and then click Next.
23 Deselect Run immediately.
24 Select Save SSIS Package.
25 Select SQL Server, if you want to store the SSIS package onto a SQL Server installation, or Structured Storage File, if you want to store the SSIS package in a file.
26 Click Next.
This opens the Save SSIS Package page. The details on this page depend on whether you chose SQL Server or Structured Storage File on the previous page.
27 Enter a Name, Description, and the other details that are required for the SSIS package.
28 Click Next, and then click Finish.
SSIS saves the SSIS package.
Requirements
▪UNICOM Intelligence Data Model
▪Microsoft SQL Server
Next
See also