Sie sind auf Seite 1von 6

Maintaining Access to Retired Databanks

The databanks PURE856, PURE93, PURE10, and AQU92 are no longer delivered with the Aspen Physical Property System. These databanks are from releases more than ten years ago, and were only intended for users who require complete compatibility with past results. Most users use newer versions of these databanks with updated information and additional components from DIPPR and other sources, and will not be affected by this change. To preserve access to these databanks for later versions of Aspen Physical Property System, follow these steps (detailed in the following sections): 1. Make a database containing a copy of the databank you are using. 2. Register the new database on all applicable computers. 3. Update existing files to use databanks from the new copy of the database. If you move to a different SQL Server installation, back up the database in the old version and restore it in the new version. (See Backing up and Restoring the Copied Databanks, below) If you do not have a version installed with these databanks, you can download the backup database APLDB from AspenTech Support, solution 128743. Once you have done that, follow the instructionsfor restoring the database at the end of this document.

Copying Retired Databanks


In order to preserve access to legacy databanks PURE856, PURE93, PURE10, and/or AQU92 that have been removed from versions after V7.2, you must make a database containing a copy of the databank you use. These instructions assume you are copying from APV72 using Aspen Properties Database Manager V7.2. You can use any later version of Aspen Properties Database Manager, or an earlier version of the enterprise database (doing so typically requires the earlier version and a recent version of the Aspen Physical Property System to both be installed).

Note: It is possible to copy a databank in other versions from 2006 to V7.1, but only by cloning the entire AP<version> database. This results in a much larger database than necessary, so the method presented here is preferred. See the help for Aspen Properties Database Manager in these versions for instructions on creating a new database using the Clone option. For each databank that you want to copy: 1 Click Start | Programs | AspenTech | Process Modeling <version> | Aspen Properties | Aspen Properties Database Manager to start Aspen Properties Database Manager. Click OK when prompted that Aspen Properties Database Manager will use an Aspen Plus or Aspen Properties license. Click the + icons to open Aspen Physical Properties Databases, then APV72, then Databanks, and locate the databank you want to copy. Right-click the name of this databank and select All Tasks | Create Databank Script File. The script file is created in the C:\Documents and Settings\All Users\Application Data\AspenTech\APED <version> folder, or a similar path under the All Users profile if it exists in a different location. 4 Optionally, edit the script file in Notepad. You can choose to reduce the component list to just the components used in your old simulations to further reduce the size of the database copy. Right-click Aspen Physical Property Databases and select Create a New Database. The Create a New Properties Database Wizard appears. Click Import Aspen Properties data transfer script (.aprdts) file, then click Next. Select the server and filename for the new database.
o o

2 3

5 6 7

Database Type Only SQL Server is supported. Server Leave this set as localhost to connect to a database on your computer, or change to .\SQLEXPRESS if this database is on SQL Server Express on your computer. If using a database server shared over the network, select the name of the server from the list. To connect to SQL Server Express, you must add \SQLEXPRESS after the computer name (or other name chosen for the specific server instance you are using). Login Name Specify apeduser. Password Specify Aprop100. Database After you specify the other settings, wait while Aspen Properties Database Manager connects to the server. Then specify the name to be used for the new database. Keep the name short, using a maximum of 8 characters. You cannot use SQL keywords (such as USER, DATABASE, TABLE, COLUMN, KEY, and INDEX) as database names.

o o o

Tip: Use the same name for this database as the databank it will contain. This will make it easier for you to remember this name later. Click Next when you are done entering this information. 8 9 Leave the Add Security box unchecked, and click Next. Click Import Files, then select the data transfer script (.aprdts file) created above. Then click Finish.

Various status messages will appear while it copies the database. At the end it will say The data conversion is completed. 10 Click Report, then click Close.

Registering the Copied Retired Databanks


When you create a new database to hold a copy of one of the retired databanks, it is automatically registered on the computer where you created it. If the Enterprise Database on this computer is also used by other computers, then on each such computer where you want to have access to the retired databank, you must register the new database. Also, when you install a new version, you need to register the database. 1 Click Start | Programs | AspenTech | Process Modeling <version> | Aspen Properties | Aspen Properties Database Manager to start Aspen Properties Database Manager. Click OK when prompted that Aspen Properties Database Manager will use an Aspen Plus or Aspen Properties license. Right-click Aspen Physical Property Databases and select Register a Database. Specify the Database Type, Server, Login Name, and Password in the same way as you did when creating the database, except that if the server was local to that computer, now you must specify the server name (perhaps with \SQLEXPRESS or another instance name following it). For the Database, select the name you specified for the new database when creating it. Click OK.

2 3 4

When the database appears in the list under Aspen Physical Property Databases, it is registered.

Updating Existing Aspen Plus and Aspen Properties Files to Use the Copied Database
After making a copy of one of the retired databanks as a new database, and registering the new database, you must update existing files to use PURE856, PURE93, PURE10, or AQU92 from the new database you created. To do so, open each one in Aspen Plus or Aspen Properties and follow these steps: 1 When prompted whether to update the databanks to the latest version, select Keep existing databanks and click OK.

2 3

Click Data | Components to open the Data Browser to the Components form. Click the Enterprise Database tab. Note: If you do not see the Enterprise Database tab, you are using the legacy databank system. You must switch to the Enterprise Database in order to use the copy of the retired databanks. See Switching Products to Use Legacy Databanks.

Under Pure component databanks and the search order, in the Available databanks list, click the databank in your new database, such as MYPURE10 PURE10 if you made a copy of the PURE10 databank in a database called MYPURE10. Click > to add it to the Selected Databanks list. Click the up arrow as many times as necessary to move it up to a position adjacent to the equivalent databank in the Aspen Properties database, such as APV72 PURE10. In the Selected Databanks list, click the name of the databank from the Aspen Properties database that you are replacing, such as APV72 PURE10. Click < to remove it from the Selected Databanks list. Save the file (under a new name or in a new folder, if desired) and use this file, rather than the original file, to maintain access to this databank with future versions of the Aspen Physical Property System which do not include the databank.

5 6

8 9

Alternatively, if you have many files to update, you can update them with any text-based search-and-replace mechanism in the .bkp and .aprbkp files. You need to know the database name from the version of Aspen Plus or Aspen Properties used to save the files as well as the new database name and the name of the databank involved. For example, if your files were saved from Aspen Plus V7.2 which uses database APV72, you are using the PURE10 databank, and you made a copy of it in a database called MYPURE10, search for "APV72 PURE10" and replace with "MYPURE10 PURE10". If you have files saved using the legacy databank system, or any version prior to version 2006, you should save them in a newer version which has all the required databanks to update them to use the Enterprise Database before you attempt this type of conversion.

Backing Up and Restoring the Copied Database


If you want to move the database to another computer, or you want to upgrade or re-install the SQL server, you should back up the database and restore it on the other computer or SQL version:

Backing up the Database


1 Click Start | Programs | AspenTech | Process Modeling <version> | Aspen Properties | Aspen Properties Database Manager to start Aspen Properties Database Manager. Right-click Aspen Physical Properties Databases and select All Tasks, then Backup Database. Select the server and filename for the new database.
o o

2 3

Database Type Only SQL Server is supported. Server Leave this set as localhost to connect to a database on your computer, or change to .\SQLEXPRESS if this database is on SQL Server Express on your computer. If using a database server shared over the network, select the name of the server from the list. To connect to SQL Server Express, you must add \SQLEXPRESS after the computer name (or other name chosen for the specific server instance you are using). Login Name Specify apeduser. Password Specify Aprop100. Database After you specify the other settings, wait while Aspen Properties Database Manager connects to the server. Then specify the name of the database to be backed up. Backup File Directory After choosing a database, a filename and directory will be generated here. Take note of this path so that you can find the file later. It can be copied from this location to another computer or backup medium as needed. Change Security Settings Do not use this option.

o o o

Click Finish when you are done entering these settings. You will see some status messages, ending with BACKUP DATABASE successfully processed and some statistics about the size of the database. Click Close.

Restoring the Database


If you are restoring the database into a newer version of Aspen Properties Enterprise Database, you should check that version's help for possible updates to the procedure for restoring a database. 1 Click Start | Programs | AspenTech | Process Modeling <version> | Aspen Properties | Aspen Properties Database Manager to start Aspen Properties Database Manager. Right-click Aspen Physical Properties Databases and select All Tasks, then Restore Database. Select the server and filename for the new database.
o o

2 3

Database Type Only SQL Server is supported. Server Leave this set as localhost to connect to a database on your computer, or change to .\SQLEXPRESS if this database is on SQL Server Express on your computer. If using a database server shared over the network, select the name of the server from the list. To connect to SQL Server Express, you must add \SQLEXPRESS after

the computer name (or other name chosen for the specific server instance you are using).
o o o

Login Name Specify apeduser. Password Specify Aprop100. Database After you specify the other settings, wait while Aspen Properties Database Manager connects to the server. Then specify the name to be used for the restored database. Keep the name short, using a maximum of 8 characters. You cannot use SQL keywords (such as USER, DATABASE, TABLE, COLUMN, KEY, and INDEX) as database names. Though this does not have to be the same as the name of the original database, you should keep it the same if you are already using it in your files. File Directory Click Browse and locate the file containing the backed up database.

Click Finish when you are done entering these settings. You will see some status messages, ending with RESTORE DATABASE successfully processed and some statistics about the size of the database. Click Close.

Das könnte Ihnen auch gefallen