| title | Moving Data Mining Objects | Microsoft Docs | |||||
|---|---|---|---|---|---|---|
| ms.custom | ||||||
| ms.date | 06/13/2017 | |||||
| ms.prod | sql-server-2014 | |||||
| ms.reviewer | ||||||
| ms.technology | analysis-services | |||||
| ms.topic | conceptual | |||||
| helpviewer_keywords |
|
|||||
| ms.assetid | bc108407-2603-4387-b930-b5bb9df78069 | |||||
| author | minewiskan | |||||
| ms.author | owend | |||||
| manager | craigg |
The most common scenarios for moving data mining objects are to deploy a model from a testing or analysis environment to a production environment, or to share models with other users.
This topic describes how you can use the tools and scripting languages provided by [!INCLUDEssASnoversion], for moving data mining objects.
You can move data mining objects between [!INCLUDEssASnoversion] databases or between instances of [!INCLUDEssASnoversion] in the following ways:
-
Re-deploying the solution to a different database.
-
Scripting individual objects.
-
Backing up and then restoring a copy of the database.
-
Exporting and importing structures and models.
The following section explains these options in more detail.
Deploying the solution to a different server or database requires that you have the solution file that was created by using [!INCLUDEssBIDevStudioFull].
For more information about deploying Analysis Services solutions, see Deploy Analysis Services Projects (SSDT).
[!INCLUDEssASnoversion] provides several languages that you can use to script objects.
-
XMLA: You can script objects using XMLA by right-clicking objects in [!INCLUDEssManStudioFull]. To execute the script, open it in an XMLA Query window on the target server.
-
DMX: You can create scripts by using templates or one of the query builders provided in [!INCLUDEssBIDevStudio] and [!INCLUDEssManStudioFull].
Note, however, that there are differences in the tasks that you can perform with each scripting language:
-
Properties such as the object description and data bindings can only by created or changed by using [!INCLUDEssASnoversion] DDL languages, not by using DMX.
-
Only DMX supports the import and export of mining objects.
-
Only DMX supports generating PMML or importing model definitions from PMML.
-
Only DMX supports training a model with application data. Moreover, the DMX INSERT INTO statement supports training a model without providing values for a key column.
For more information, see Developing with Analysis Services Scripting Language (ASSL).
Backup and restore of an entire Analysis Services database is the method of choice if your data mining solution relies on OLAP objects. [!INCLUDEssCurrent] provides backup and restore functionality that makes database backups faster and easier.
For more information about backup, see Backup and Restore of Analysis Services Databases.
Exporting and then re-importing mining models and structures by using DMX statements is the easiest way to move or back up individual relational data mining objects. For more information about the DMX syntax for these operations, see the following topics:
If you specify the INCLUDE DEPENDENCIES option, [!INCLUDEssASnoversion] will also export the definition of any required data source views, and when you import the model or structure, it will re-create the data source view on the target server. After you have finished importing the model, make sure to set the necessary mining permissions on the object.
Note
You cannot export and import OLAP models by using DMX. If your mining model is based on an OLAP cube, you must use the functionality provided by [!INCLUDEssASnoversion] for backing up and restoring an entire database, or redeploy the cube and its models.