ApexSQL Knowledgebase: How to migrate from ApexSQL Edit 2008.05 to 2008.06 if you have a database mapped to a Source Control system using the CUSTOM mapping pattern?

LINKS

General

ApexSQL Audit
ApexSQL Clean
ApexSQL Data Diff
ApexSQL Debug
ApexSQL Diff
ApexSQL Diff API
ApexSQL Doc
ApexSQL Edit
ApexSQL Enforce
ApexSQL Log
ApexSQL Log API
ApexSQL Recover
ApexSQL Refactor
ApexSQL Script
ApexSQL Source Ctl
ApexSQL SSIS Compare

Knowledgebase Home

SITE FEED

Site Feed

Support Forum

The fastest and most effective to get answers to your questions quickly.

FAQs

Quick answers to common questions.

Troubleshooting

Known issues and basic troubleshooting techniques for problems or unexpected behaviors.

Knowledgebase

Technical tips, How-to articles, and other tutorials about ApexSQL Tools.

Online Documentation

All of our help files for download or convenient viewing online.

Videos

Watch product demos, training videos, or tutorials of our products' main features.

ApexSQL Knowledgebase

Tips and How-to Articles for ApexSQL Tools

How to migrate from ApexSQL Edit 2008.05 to 2008.06 if you have a database mapped to a Source Control system using the CUSTOM mapping pattern?

DESCRIPTION
This article describes how to migrate from ApexSQL Edit 2008.05 to 2008.06 or higher if you have a database mapped to a Source Control system using the custom mapping pattern.

SOLUTION
A mapping pattern defines a way of scripting database objects to Source Control: it includes file name templates and subprojects for each object type.

Let’s assume that you have mapped a database to a Source Control system using the following settings in ApexSQL Edit 2008.05:

a) Scripts for each database object type were stored in a separate Source Control project, like displayed below:

   b) Script file names consist of the schema name, object name and ‘sql’ extension (for example dbo.Table1.sql).

Follow the procedure described below to map your database to the existing Source Control project defined in ApexSQL Edit 2008.05 using ApexSQL Edit 2008.06 (Microsoft Visual SourceSafe 2005 is used as an example of the Source Control system):

   1. Install ApexSQL Edit 2008.06 in a separate folder leaving ApexSQL Edit 2008.05 in its old folder.
   2. After you have started ApexSQL Edit 2008.06 your databases appear not mapped to a Source Control system even if they were mapped in the previous ApexSQL Edit version.
   3. Right click the database that is to be mapped to the existing Source Control project created using the previous version of ApexSQL Edit and select the Set up Source Control command from the Source Control menu.

4. Select the Microsoft Visual SourceSafe from the available Native Source Control systems and click the Next button.
5. Enter the Source Control Login information as displayed below:

Remember to select the same Source Control database as it was used by the ApexSQL Edit 2008.05 version, the same Source Control project and the same working folder.
You can click the Test button to verify if you can access your Source Control database/project using the parameters entered on the Source Control Login tab.

6. Then click the Advanced button to display additional Source Control Wizard steps and click Next.

Click in the Subfolder name edit box and change the default subfolder names to the ones you defined in ApexSQL Edit 2008.05 (for example delete the default text “Functions” and enter the “Funcs”, then change the subfolder names for other database object types).

Note: If a Central database was used in ApexSQL Edit 2008.05, then:
a) The first user who is migrating to the newer version should export all current settings defined in the Advanced | Configure Mappings tab to an xml file using the Export… button.
b) Each next user who is migrating to the newer application version should import settings exported by the first user using the Import button.

After you have clicked the Next button ApexSQL Edit 2008.06 automatically maps database objects stored in a database to script files stored in a Source Control project based on the scripts file names.

Click the Finish button to complete the Source Control Wizard and the migration procedure. Your database and database’s objects are shown now as mapped to a Source Control system.

SEE ALSO
How to migrate from ApexSQL Edit 2008.05 to 2008.06 if you have a database mapped to a Source Control using the IMPLICIT mapping pattern?

AUTHOR
Anna Lesniak

LAST REVIEW DATE
07 August 2009

Labels: Apex SQL Edit, Source Control

posted by Anna Lesniak on Friday, August 07, 2009

0 Comments: