Exporting UNICOM Intelligence data to Quantum
Note For information on working with the SQL Server Import and Export Wizard, see:
http://technet.microsoft.com/en-us/library/ms141209(SQL.90).aspx
This topic shows you how to use the SQL Server Integration Services Import/Export wizard to take data that was collected using one of the UNICOM Intelligence products (for example, UNICOM Intelligence Interviewer) and that is stored in a relational MR database and export it to a Quantum-format ASCII file, so that you can analyze it using Quantum.
Before you can export the data, you may need to use
Metadata Model to Quantum to set up the card and column definitions in the questionnaire definition. Whether you need to do this or not depends on how the questionnaire has been defined, and whether the data was collected using a version of the UNICOM Intelligence products that is compatible with the one you are using now. For example, if you want to transfer data gathered with UNICOM Intelligence Interviewer to Quantum using a recent version of UNICOM Intelligence Data Model, you must run Metadata Model to Quantum or use the Metadata Model to Quantum component to update the data to match the format expected by UNICOM Intelligence Data Model (UNICOM Intelligence Data Model uses additional system variables). Card and column definitions are required in all of the versions of the questionnaire definition that you use for the export.
To export data collected using more than one version of the questionnaire definition (.
mdd) file, see
Version handling in Metadata Model to Quantum.
1 From the Windows Start menu, choose: Programs > Microsoft SQL Server > Microsoft SQL Server Management Studio
2 Right-click the database and select Tasks > Export Data.
This opens the first page of the SQL Server Import and 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 UNICOM Intelligence Metadata Document.
6 Enter the Metadata Location, either by typing the name and location of the .mdd file into the text box, or by clicking Browse and selecting it in the Open dialog box.
7 If you want to select one or more particular versions of the metadata to use for the export, click
Properties, and then select the version or versions you require. Card and column definitions are required in all of the versions that you select here. For more information, see
Working with versions.
8 From the Case Data Type list, select UNICOM Intelligence Database (MS SQL Server) (read-write).
9 Generally, the
Case Data Location defaults to the connection string defined in the .
mdd file when the project was activated and you do not need to change it. However, if necessary you can enter the connection string manually. For more information, see
Connecting to a relational MR database using RDB DSC 2.
10 If necessary enter your Login ID and Password, and then click OK.
11 Enter the Case Data Project, and then click Test Connection.
If Test connection failed is displayed, check that you have entered all of the details correctly. If relevant, check your network connection to the server where the database is.
12 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 Select Destination page of the SQL Server Import/Export wizard.
13 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.
14 From the Metadata Type list, select Intelligence Metadata Document.
15 Enter the Metadata Location, either by typing the name and location of the .mdd file into the text box, or by clicking Browse and selecting it in the Open dialog box. This should be the same .mdd file that you specified previously.
16 If you previously selected one or more particular versions of the metadata to use for the export, click
Properties and select the same version or versions that you selected before. For more information, see
Working with versions.
17 From the Case Data Type list, select Quantum Data File (DAT) (read-write).
18 Enter the Case Data Location, either by typing the name of the .dat file to which you want to export the data, or by clicking Browse and selecting it in the Select Data Source dialog box. You can specify a new file name or the name of an existing .dat file.
19 Leave the Case Data Project text box blank.
20 Select the Advanced tab and choose the data validation options that you require.
21 Select the Connection tab, and then click Test Connection.
Test connection succeeded means that you have entered all of the details correctly and the data can be exported to the specified .dat file.
If Test connection failed is displayed, check that you have entered all of the details in this dialog box correctly and check that you have used Metadata Model to Quantum to set up the card and column definitions in the questionnaire definition. If you chose on the Advanced tab to validate the data and there are any errors in the data, Quantum DSC displays the first error message. If you want to export the data anyway, go back to the Advanced tab and deselect Perform data validation.
22 Click OK to return to the Choose a Destination page of the SQL Server Import/Export wizard, and then click Next.
23 Do one of the following:
▪To export all of the data, select Copy table(s) and view(s) from the source database and then continue through the instructions in this topic.
24 Click Next.
25 Select the VDATA table for both the Source and Destination, and then click Next.
26 Select when you want to run the export.
27 If you want to save the export specifications as a SSIS package that you can run again, select Save SSIS Package. Select SQL Server, if you want to store the SSIS package in a SQL Server, or Structured Storage File, if you want to store the SSIS package in a file.
28 Click Next.
If you chose to save the export as a SSIS package, 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.
29 Enter a Name, Description, and the other details that are required for the SSIS package.
30 Click Next, and then click Finish.
If you chose to run the export immediately, SSIS now exports the data, although the SSIS package is saved first, if you chose that option.
The wizard tells you whether any errors were encountered. Double-click the appropriate line to see the error messages. If there is an error message with the text Failed to load MDM document. Permission denied, file already open, save the export as a SSIS package using the SQL Server option. You then need to make a small change to it before you can run it in SQL Server Management Studio. (If you did not choose the option to save the package, you can do so now by going back to the Save, Schedule, and Replicate Package page.)
For information about Quantum DSC error and warning messages, see
Quantum DSC error and warning messages.
By default, open-ended responses are written to a .dau file. You can stop a text variable going into the .dau file by defining allocations manually in Metadata Model to Quantum.
Requirements
UNICOM Intelligence Data Model
Microsoft SQL Server
See also