Repeat the linking process as for the initial linking to depot. To unlink a database, right click it and from the More source control options menu, selected the Remove link to source control option:
This means that we need to unlink the database from the current branch ( depot) and re-link it to the newly created branch ( TestBranch). In order to switch between branches, we’ll need to re-link the database. If a new branch is correctly created, there should be a difference shown in the Action center tab. In that way, it will be compared to a current state of a database which already contains changed AddressType table. In order to verify that the most recent change, related to the AddressType table, is not included let’s make the TestBranch as the active branch. As shown in the image below, identical folder structure that was created in deport, is replicated in TestBranch: To verify that a new branch is created, we can explore a repository structure. When the process is finished, a validation message appears: Once we have everything set, by clicking the OK button, a new branch will be created and all the content from the source branch will be copied to a folder dedicated to a new branch, except for changes related to the AddressType table. We’ll specify TestBranch to be the target branch: The Target field is where a name for the new branch should be specified. In general, anything that is committed after the selected changeset will not be included in a new branch, while any changes committed before the selected changeset will be included. In this case, we have one commit that represents the initial commit (Version 16) and another one that represents an additional change related to the AddressType table (Version 18).Īs we don’t want to include anything after the initial commit, we’ll highlight the changeset 16.
In this case it is depot:īelow the Source field is a list of changesets that are committed to a source branch. The source branch will be automatically set to a branch where a database is linked. In order to create a new branch, right click a database and choose the Create branch option from the More source control option context menu: Since we have two changesets, the one that represents the initial commit of all objects and another one that contains a change related to the AddressType table, the second changeset will not be included in a new branch. Now that we have additional change committed to source control, let’s create a new branch. We’ll commit this change to a Perforce depot: Let’s make additional change in a database using the following script: Now that we have a database linked to source control, let’s initially commit all objects by specifying a commit message and clicking the Apply button:
In order to link a database to a Perforce depot, we’ll specify that in the final step of the Source control wizard: We’ll link a database to a Perforce repository, specifically to a default depot that will be used as a main line in this article.
PERFORCE DOWNLOAD DEPOT HOW TO
In order to switch to a newly created branch, we’ll have to re-link a database choosing a new branch in the linking process.Īt the end, we’ll merge changes from two branches and confirm that the merging process ended successfully by comparing a database with both of the branches, the main one and the newly created one.Ī local Perforce repository will be used, but the same workflow can be applied for a Perforce repository hosted in any other way.ĭetailed explanation about the linking process to a Perforce repository is already covered in the article: How to link a SQL Server database to a Perforce repository Linking a database to a main branch Some changesets committed to the main branch will not be included in a new branch and those should be shown as a difference after switching to a new branch. Next, we’ll create a new branch that will contain only selected changesets. Besides the initial commit of all database objects, we’ll make additional changes for the purpose of showing how to create a branch that includes specific changesets. We’ll first link a database to a branch that will be used as a main line. Since a depot is used in Perforce as an equivalent to a source control project/repository, in this article, it is assumed that each branch is a new depot.
0 kommentar(er)
