426
SQL Server 2012 Upgrade Technical Guide
Figure 2: Results of the analysis of the SQL Server 2005 data mining models
You can also expect to have no unresolved issues found in your SSAS 2005 data mining
models when you run Upgrade Advisor. (Similarly, there should be no unresolved issues
found in SSAS 2008 and 2008 R2 models.) However, this does not mean that you
should just upgrade the 2005 models. You should also perform post-upgrade tasks. As
we will show you later in this chapter, it makes sense to revise the 2005 predictive and
forecasting models after upgrading to SSAS 2012.
Upgrading from SQL Server 2005
In Chapter 1, you learned how to start the SQL Server 2012 Setup program and perform
an in-place and side-by-side upgrade. This section assumes that you have already
installed SQL Server 2012, so we will not describe that process here. Instead, we will
focus only on data mining issues you might face in your upgrade from SSAS 2005 to
SSAS 2012. As you will see, the in-place upgrade is somewhat simpler, but the side-by-
side upgrade strategy gives you more options for migrating mining models.
427
SQL Server 2012 Upgrade Technical Guide
To demonstrate upgrading data mining models from SQL Server 2005 to SQL Server
2012, let’s consider a sample SSAS 2005 database that has a data source from the SQL
Server 2005 AdventureWorksDW demo database, a data source view with all necessary
database views included (vTargetMail, vTimeSeries, vAssocSeqOrders, and
vAssocSeqLineItems), and seven data mining models in four data mining structures.
Four predictive models use the same structure, based on vTargetMail. The models try
to predict whether a customer is likely to buy a bike using demographic data and four
algorithms (Decision Trees, Naïve Bayes, Neural Network, and Clustering). The Time
Series mining model has its own structure, based on the vTimeSeries view, for
forecasting the sales quantity and amount for bike models in different regions. The
Association Rules algorithm model uses the vAssocSeqOrders and vAssocSeqLineItems
database views to try to find out which products are sold together. Although the
Sequence Clustering algorithm uses the same source database views, it has its own
structure, with the keys defined differently than in the structure for the Association
Rules model. Sequence Clustering tries to find not only which products are sold
together but also the order of products in a transaction. Figure 3 shows the columns
usage for Association Rules, and Figure 4 shows the columns usage for Sequence
Clustering.
Figure 3: Columns usage for Association Rules
428
SQL Server 2012 Upgrade Technical Guide
Figure 4: Columns usage for Sequence Clustering
All objects in the SSAS 2005 database that need to be upgraded for data mining
models in our case include a data source, a data source view, and four mining
structures with seven mining models, as shown in Figure 5.
Figure 5: SSAS 2005 database with all objects that need to be upgraded
429
SQL Server 2012 Upgrade Technical Guide
In-Place Upgrade
You start an in-place upgrade from SSAS 2005 to SSAS 2012 by running SQL Server
Setup. The upgrade process is painless for the data mining models. Your SSAS
databases are automatically upgraded, and you can continue using your mining models
the same way you used them in SSAS 2005. In addition, you can use your SSAS 2005
mining projects in SSDT 2012 to continue with development. When you open the SSAS
2005 data mining project in SSDT 2012 for the first time, the Visual Studio Conversion
Wizard is launched automatically, and your project is converted to version 2012.
Consider using a version control system to maintain previous versions, or back up the
project manually before you convert it to SSDT 2012. Figure 6 shows how the Visual
Studio Conversion Wizard launches when you open a BIDS 2005 project.
Figure 6: SSDT 2012’s Visual Studio Conversion Wizard launches when you open a
BIDS 2005 project
If you want to perform an in-place upgrade, run SQL Server Setup and select the
Upgrade from SQL Server 2005, SQL Server 2008 or SQL Server 2008 R2 link from the
Installation tab of the SQL Server Installation Center, as shown in Figure 7.
430
SQL Server 2012 Upgrade Technical Guide
Figure 7: Select the Upgrade link for an in-place upgrade
Because the upgrading process was already described in previous chapters, we are not
showing all the details here. Just be sure to select the correct SSAS 2005 instance. The
upgraded instance will be in Multidimensional and Data Mining mode; there is no in-
place upgrade to SSAS 2012 Tabular mode available from SQL Server Setup. Note that
after the upgrade, SQL Server 2005 tools such as SQL Server Management Studio
(SSMS) are still left on the computer. However, you cannot use SSMS 2005 to connect
to a SSAS 2012 database, as shown in Figure 8. Naturally, you should be able to
connect to the upgraded instance with SSMS 2012.
Figure 8: Message when you try to connect to an SSAS 2012 instance with SSMS 2005
Dostları ilə paylaş: |