The current version of DBAmp is Version 2.14.9. You can view the fixed issues and enhancements by version here.

If you are upgrading an existing DBAmp installation, please follow these steps:

1. Download either www.forceamp.com/hats/dbamp_pro.zip (for 32 bit SQL Server) or www.forceamp.com/hats/dbamp_x64.zip (for 64 bit SQL Server).
2. Stop SQL Server.
3. Run the DBAmp installation program. You will need your serial number for installation. Please contact support at forceamp.com if you need help with this value.
4. Restart SQL Server
5. The DBAmp stored procedures change with every release. You must upgrade every SQL database that currently contains DBAmp stored procs with the new versions. Update the DBAmp Stored Procedures by running the Program Files/DBAmp/SQL/Create DBAmp SPROCS.sql file. You must modify all instances of the @ProgDir variable in the script if you installed DBAmp in another directory other than c:\Program\Files\DBAmp . Failure to do this will result in errors.
6. Because the new version may connect to a newer API endpoint, additional fields and objects may become visible with the upgrade. If you are using sf_refresh for local copies, you must run sf_replicate on that object to pickup these schema changes. Then you can resume your normal sf_refresh schedule.

Note that there are 3 major, breaking changes that have occurred recently with DBAmp.

- OpenQuery support for SOQL. Previous versions of DBAmp allowed a mixture of SQL or limited SOQL in the OpenQuery phrase. The current version of DBAmp allows only SOQL in an OpenQuery.

- SF_BulkOps Error handling. SF_BulkOps now writes the phrase Operation Successful into the Error column for rows that were successfully processed. The previous versions of DBAmp wrote a single blank. You must modify your post sf_bulkops integration to handle the new behavior. Alternatively, you may use the BulkOpsCompatibility registry switch. See the chapter DBAmp Registry Settings for more information.

- SQL 2008 and datetime2(7). On SQL 2008 systems, date and datetime fields of salesforce.com objects are now created as datetime2(7) fields in the local database. To force these fields to be created as datetime fields instead, set the Database Compatibility Level of the Salesforce backup database to 90 prior to replicating the data (step 5 above). This change applies to SQL 2008 only.

As always, if you need help with this process, please send an email with the specific problems you are having to support at forceamp.com.