| LINKS |
|
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 using the IMPLICIT 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 implicit mapping pattern. SOLUTION The implicit mapping pattern is used by default in ApexSQL Edit 2008.05 and means that: a) Scripts for database’s objects were stored in the same Source Control project, 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.0164 your databases are 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. Important! Deselect all check boxes for the Subfolder column on the Configure Mappings tab and click the Next button.  Note: If a Central database was used in ApexSQL Edit 2008.05.0163, 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.0164 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 system using the CUSTOM mapping pattern? How can I define the Source Control parameters when I set up different Source Control systems using native drivers in the Source Control Wizard? How to map a database to a Source Control system step by step? AUTHOR Anna Lesniak LAST REVIEW DATE 24 July 2009 Labels: Apex SQL Edit 2 Comments:At October 7, 2009 8:46 AM, sdfasf said...
Apparently Apex source control cannot connect to a subversion repository using the svn:// protocol? At December 7, 2009 9:55 AM, Dejan Apostolovic said...
Hello, << Home |
