Migrating to SQL Server 2. SQL Server 2. 01. In Memory OLTP, with its 2x 3. Sql Anywhere Developer Edition License Check' title='Sql Anywhere Developer Edition License Check' />The best new features in SQL Server 2014 probably wont come with the cheap prices or licensing. Learn why the release date will probably be an expensive one. HowTo Details. This HowTo tutorial focuses on version 17 of the SAP SQL Anywhere Developer Edition and Raspberry Pi 3 Model B. Other Linux distributions and other. CloudDest1.png' alt='Sql Anywhere Developer Edition License Check' title='Sql Anywhere Developer Edition License Check' />SQL Server 2. SQL Server 2. 01. SQL Server 2. 01. There are two basic strategies for upgrading to a new SQL Server release. Some people recommend performing a full backup followed by a clean install of SQL Server on a new operating system. Other people prefer performing in place upgrade. Each different tact has their advantages. Full Backup Followed by Clean Install. People who prefer the clean upgrade say you minimize the register and system corruption that eventually creeps into all Windows installation. Thereby giving you a more stable new installation. This is essentially the same as performing a new installation. However, this method is time consuming and costly. You need to restore all of your databases and in many cases need to buy a new Windows Server OS license. Then you need to restore any custom SQL Server settings and properties that you may have changed. In Place Upgrade is Much Faster. Alternatively, performing an in place upgrade is much faster as you only need to install the need SQL Server version over top of the old one. Theres no need to backup and restore. Some database pros say this method is safer because you know youll be running with the same settings and they dont like to change an otherwise stable system. I have performed both successfully many times in the past. In this article Ill cover the steps for performing an in place upgrade of SQL Server 2. SQL Server 2. 01. You can perform an in place upgrade to SQL Server 2. Installation Center or you can upgrade by running setup. In this article Ill guide you through the setup of migrating to SQL Server 2. Installation Center. For more information about using a configuration file you can refer to Install SQL Server 2. Using a Configuration File. The SQL Server 2. SQL Server. SQL Server 2. SP1. SQL Server 2. R2 SP2. SQL Server 2. SP3. SQL Server 2. You cannot perform an in place upgrade for older versions of SQL Server such as SQL Server 2. SQL Server 7. 0, or SQL Server 6. In addition, you cannot add features during the upgrade process. In general, you can upgrade from your current edition to of SQL Server to the equivelant or higher editions. For instance, you can upgrade from the SQL Server 2. R2 SP2 Datacenter edition the highest for that release to the SQL Server 2. Enterprise or Business Intelligence editions. Likewise, you can upgrade for the SQL Server 2. SP1 to the SQL Server 2. Standard, Enterprise, or Business Intelligences editions. The Developer Edition can only be upgraded to the Developer Edition. For a complete list of supported upgrade paths to SQL Server 2. Supported Version and Edition Upgrades. SQL Server 2. 01. Hardware Requirements. SQL Server 2. 01. The minimum processing requirement for a 3. GHz CPU, while the 6. GHz processor. Microsofts recommended minimum processor speed is 2. GHz. The minimum memory requirements for SQL Server 2. The low end SQL Server 2. Express edition requires a minimum of 5. MB while the other editions require a minimum of 1 GB or RAM. Microsofts recommended minimum RAM for the SQL Server 2. Standard edition and above is 4 GB. Disk space requirements vary depending on the features that you install. SQL Server 2. 01. GB of free disk space. SQL Server 2. 01. Operating System Requirements. SQL Server 2. 01. SQL Server 2. 01. In addition, the 3. SQL Server 2. 01. The following table lists all the supported operating systems for the principle editions of SQL Server 2. SQL Server 2. 01. Edition. 32 bit. SQL Server 2. Enterprise. Windows Server 2. R2 6. 4 bit Datacenter. Windows Server 2. R2 6. 4 bit Standard. Windows Server 2. R2 6. 4 bit Essentials. Windows Server 2. R2 6. 4 bit Foundation. Windows Server 2. Datacenter. Windows Server 2. Standard. Windows Server 2. Essentials. Windows Server 2. Foundation. Windows Server 2. R2 SP1 6. 4 bit Datacenter. Windows Server 2. R2 SP1 6. 4 bit Enterprise. Windows Server 2. R2 SP1 6. 4 bit Standard. Windows Server 2. R2 SP1 6. 4 bit Web. Windows Server 2. SP2 6. 4 bit Datacenter. Windows Server 2. SP2 6. 4 bit Enterprise. Windows Server 2. SP2 6. 4 bit Standard. Windows Server 2. SP2 6. 4 bit Web. Windows Server 2. SP2 3. 2 bit Datacenter. Windows Server 2. SP2 3. 2 bit Enterprise. Windows Server 2. SP2 3. 2 bit Standard. Windows Server 2. SP2 3. 2 bit Web. Windows Server 2. R2 6. 4 bit Datacenter. Windows Server 2. R2 6. 4 bit Standard. Windows Server 2. R2 6. 4 bit Essentials. Windows Server 2. R2 6. 4 bit Foundation. Windows Server 2. Datacenter. Windows Server 2. Standard. Windows Server 2. Essentials. Windows Server 2. Foundation. Windows Server 2. R2 SP1 6. 4 bit Datacenter. Windows Server 2. R2 SP1 6. 4 bit Enterprise. Windows Server 2. R2 SP1 6. 4 bit Standard. Windows Server 2. R2 SP1 6. 4 bit Web. Windows Server 2. SP2 6. 4 bit Datacenter. Windows Server 2. SP2 6. 4 bit Enterprise. Windows Server 2. SP2 6. 4 bit Standard. Windows Server 2. SP2 6. 4 bit Web. SQL Server 2. 01. Business Intelligence. Windows Server 2. R2 6. 4 bit Datacenter. Windows Server 2. R2 6. 4 bit Standard. Windows Server 2. R2 6. 4 bit Essentials. Windows Server 2. R2 6. 4 bit Foundation. Windows Server 2. Datacenter. Windows Server 2. Standard. Windows Server 2. Essentials. Windows Server 2. Foundation. Windows Server 2. R2 SP1 6. 4 bit Datacenter. Windows Server 2. R2 SP1 6. 4 bit Enterprise. Windows Server 2. R2 SP1 6. 4 bit Standard. Windows Server 2. R2 SP1 6. 4 bit Web. Windows Server 2. SP2 6. 4 bit Datacenter. Windows Server 2. SP2 6. 4 bit Enterprise. Windows Server 2. SP2 6. 4 bit Standard. Windows Server 2. SP2 6. 4 bit Web. Windows Server 2. SP2 3. 2 bit Datacenter. Windows Server 2. SP2 3. 2 bit Enterprise. Windows Server 2. SP2 3. 2 bit Standard. Windows Server 2. SP2 3. 2 bit Web. Windows Server 2. R2 6. 4 bit Datacenter. Windows Server 2. R2 6. 4 bit Standard. Windows Server 2. R2 6. 4 bit Essentials. Windows Server 2. R2 6. 4 bit Foundation. Windows Server 2. Datacenter. Windows Server 2. Standard. Windows Server 2. Essentials. Windows Server 2. Windows Server 2. R2 SP1 6. 4 bit Web. Windows Server 2. SP2 6. 4 bit Datacenter. Windows Server 2. SP2 6. 4 bit Enterprise. Windows Server 2. SP2 6. 4 bit Standard. Windows Server 2. SP2 6. 4 bit Web. SQL Server 2. 01. Standard. Windows Server 2. R2 6. 4 bit Datacenter. Windows Server 2. R2 6. 4 bit Standard. Windows Server 2. R2 6. 4 bit Essentials. Windows Server 2. R2 6. 4 bit Foundation. Windows Server 2. Datacenter. Windows Server 2. Standard. Windows Server 2. Essentials. Windows Server 2. Foundation. Windows Server 2. R2 SP1 6. 4 bit Datacenter. Windows Server 2. R2 SP1 6. 4 bit Enterprise. Windows Server 2. R2 SP1 6. 4 bit Standard. Windows Server 2. R2 SP1 6. 4 bit Foundation. Windows Server 2. R2 SP1 6. 4 bit Web. Windows 8. 1 3. 2 bit. Windows 8. 1 Pro 3. Windows 8. 1 Enterprise 3. Windows 8. 1 6. 4 bit. Windows 8. 1 Pro 6. Windows 8. 1 Enterprise 6. Windows 8 3. 2 bit. Windows 8 Professional 3. Windows 8 6. 4 bit. Windows 8 Professional 6. Windows 7 SP1 6. 4 bit Ultimate. Windows 7 SP1 6. 4 bit Enterprise. Windows 7 SP1 6. 4 bit Professional. Windows 7 SP1 3. 2 bit Ultimate. Windows 7 SP1 3. 2 bit Enterprise. Windows 7 SP1 3. 2 bit Professional. Windows Server 2. SP2 6. 4 bit Datacenter. Windows Server 2. SP2 6. 4 bit Enterprise. Windows Server 2. SP2 6. 4 bit Standard. Windows Server 2. SP2 6. 4 bit Foundation. Windows Server 2. SP2 6. 4 bit Web. Windows Server 2. How To Set Adobe Reader As Default Program here. Deploying an SAP SQL Anywhere Database Application Using the Wi. X Toolset. This document describes how to deploy an SAP SQL Anywhere database alongside a Windows application using an installation package created with the Wi. X toolset. Introduction. Windows Installer i. MSI is a popular method for packaging Windows applications for deployment. There are many ways to create MSI install packages and an easy method is to use the Windows Installer XML Wi. X Toolset. This set of tools provides developers with a quick way of packaging a Windows application for distribution and this document describes how to deploy an SAP SQL Anywhere database alongside a Windows application using an installation package created with the Wi. X toolset. There are other ways to achieve the same result, such as using other software such as Install. Shield or by copying the required files. If you interested in those methods, please refer to the document Embedding SAP SQL Anywhere 1. Commercial Applications Requiring a Database available here http scn. DOC 4. 35. 50. Prerequisites. The steps described in this document were tested under Windows XP and Windows 7 3. SAP SQL Anywhere 1. Visual Studio 2. 01. Wi. X Toolset 3. 7. The ADO. NET sample application used in the Wi. X deployment packages requires. NET Framework 3. 5 to run. This document describes deployment for a Windows application. The steps will be similar for other operating systems. See the SQL Anywhere documentation for more information http dcx. Preparation. In this document well be deploying the SQL Anywhere ADO. NET Simple. Viewer sample application that is included in the SQL Anywhere installation. The Visual Studio source code is provided and must be compiled. For the Wi. X Toolset deployment method, a subset of database engine files must be assembled in your computer. The ADO. NET sample used in the deployed application requires SQL Anywhere. NET assemblies. For installation instructions on how to deploy SQL Anywhere. NET components, see the document http dcx. Please note that the SQL Anywhere. NET assemblies are installed automatically if Visual Studio is installed prior to SQL Anywhere. Building the Simple. Viewer Sample. Compile the sample application using Visual Studio Launch Visual Studio. Select File Open ProjectSolution. Open the Simple. Viewer solution file it is found at SQLANYSAMP1. SQL Anywhere 1. 6SamplesSQLAnywhereADO. NETSimple. Viewer. By default, this path resolves to C Documents and SettingsAll UsersDocumentsSQL Anywhere 1. SamplesSQLAnywhereADO. NETSimple. Viewer on Windows XP and C UsersPublicDocumentsSQL Anywhere 1. SamplesSQLAnywhereADO. NETSimple. Viewer on Windows Vista and Windows 7. Select the solution Simple. Viewer. sln and click OK. If running Visual Studio 2. You can go ahead and do that. Open Build Configuration Manager. Change the Active solution configuration to Release. Make sure the Simple. Viewer project shows Release as its selected configuration. Open Project Simple. Viewer Properties. Change Target framework to. NET Framework 3. 5. Chose Build Build Solution. This compiles the Simple. Viewer project as a. NET executable and places the file in the sample project directory inside the folder binRelease. Note that this sample application is compiled for. NET Framework 3. 5. If you wish to compile for other versions of. NET, simply change the target framework under project properties and add the appropriate version of SQL Anywhere ADO. NET data provider. Shut down Visual Studio. Preparing Database Engine Files. To simplify the process, it is recommended that you place all the files required to run the application inside a single folder. Create a folder C Simple. Viewer. Files and copy the necessary files there are 1. Application Executable 2. KB Simple. Viewer. Database 3. 7 MB demo. Database Server Binaries 2. MB dbcis. 16. dll, con. Server License File 1 KB dbeng. Connectivity Library 2. MB i. Anywhere. Data. SQLAnywhere. Database Utilities 8. KB dbelevate. 16. All these files are needed to deploy the Simple. Viewer sample application. Included are several connectivity libraries needed to establish a database connection with. NET applications and the demo database. In total this deployment including the database, database engine and application executable only requires approximately 3. MB of disk space. The Wix Toolset. The Wi. X Toolset builds Windows installation packages from XML source code. This document uses the Wi. X Toolset to copy the Simple. Viewer application and SQL Anywhere binaries, and create its ODBC data source. This document uses the Wi. X Toolset 3. 7, but is applicable to other versions as well. It is worth noticing that the installer package we are about to create does not have a user interface i. It also does not check whether the target computer already has the. NET Framework installed. If you would like to add a user interface and perform checks during the installation, please consult the Wi. X Toolset documentation for instructions on how to code those operations. For reference, the appendix at the end of this paper has a code listing that does exactly that. Building the Installer. Launch Visual Studio 2. On the left panel, select Installed Templates Windows Installer XML and choose Setup Project. Type a name e. g. Simple. Viewer. Installer and a location for the project e. C Simple. Viewer. Installer. Make sure the project is using. NET Framework 3. 5. Note if you do not see the Windows Installer XML project template, then you do not have the Wi. X Toolset installed. Please install it before proceeding. In Solution Explorer, right click on Simple. Viewer. Installer Add Existing Item. Browse to the Simple. Viewer. Files directory you created earlier. Select all the files and click the Add button. Open the file Product. Modify the Product start tag to change the Name, Language, version, Manufacturer, and the Upgrade Code. Product. IdNameSimple. ViewerLanguage1. Version1. ManufacturerSAP Upgrade. Code8. 81e. 72. Important For a 6. Package tag to include the Platform attribute and set it to x. Package. Installer. Version2. 00CompressedyesInstall. Scopeper. Machine Platformx. Enter Simple. Viewer as the product name in Major. Upgrade tag. lt Major. Upgrade. Downgrade. Error. MessageA newer version of Simple. Viewer is already installed. Modify the directory tag as follows to deploy the application to C SQL Anywhere DemosSimple. Viewer. lt Directory. IdTARGETDIRNameSource. Dir   lt Directory. IdSQLAnywhere. DemosNameSQLAnywhere Demos      lt Directory. IdINSTALLFOLDERNameSimple. Viewer    lt Directory lt Directory For this project, we will create two components, Product. Component and Demo. Data. Source. Since we will only create components, delete the Component. Group that is created by default. Modify the Feature tag as follows to reference to these two components. Feature. IdProduct. FeatureTitleSimple. Viewer. InstallerLevel1   lt Component. Ref. IdProduct. Component    lt Component. Ref. IdSA1. 6Demo. Data. Source lt Feature For each component, it is necessary to add a GUID attribute. To create a GUID in Visual Studio, click on Tools Create GUID. Change the Format to Registry Format and click on Copy. Add a new Fragment to contain the Product. Component element.