TFS 2008 Branching always adds root folder - branching-and-merging

I'm trying to create a branch for QA using TFS 2008
I have my main code in the trunk folder.
When I perform the branch, I select a qa folder which I created to be mirror the trunk folder.
However, when I perform the branch, it puts the trunk folder inside the qa folder, which is not what I want. I want the qa folder to be a mirror of the trunk folder.
Is this possible with TFS 2008?

Are you performing the branch operation from the root of the team project, or from the Trunk folder itself? If you are branching from the root, then any branch created will contain the Trunk folder, whereas if you branch directly from the Trunk folder your QA folder should mirror what's in the Trunk folder.

Related

Restore database without dump but files --> /var/lib/mysql

I want to know if it is possible to restore my database without dump.
In fact, I had a problem with mysql on my debian 9 server. I uninstall debian and reinstate it. I lost everything but before uninstall debian, I saved ib_logfile0, ib_logfile1 and ibdata1 files and the database folder with the database name. There files and folder was located in /var/lib/mysql
I already tried to copy and paste the files and the folder on my new debian but it doesn't work...
Is it possible to restore the database with this 3 files and this folder (on the folder, there is .frm and .ibd files) ?
If you have the entire folder, then you effectively have the entire dataset. The two things that are elsewhere:
The MySQL code -- It would be wise to install the same version 5.xx.yy.
The config file(s) -- /etc/my.cnf (or wherever). You may have to reconstruct it. The one tricky setting (if you had changed it) is innodb_log_file_size.
I am not sure if there are other critical files in the directory other than the 3 files you mentioned.
Give it a try.

The system database file master.mdf already exists in C:\

I am trying ti add some new features to my already installed Sql Server instance.
I run the installation setup and chose the option to add new features to existing instance of Sql Server 2016 RC3. Checked the options I wanted to add and then continued to next step. At the step where I add Authentication Mode and the server administrators I am having an error like below in the image.
The problems is obvious but is it obligatory to 'delete' master.mdf file and tempdb.mdf file before starting the installation or do something else ?
I dont want to change the locations of the master db files because I dont want to create two directories for the same purpose with two databases with the same purpose again.
Open Explorer and navigate to the folder in question (in my case):
C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\DATA
Control-A (select all), Control-X (cut)
Create a new folder: DATA_OLD
Go into the DATA_OLD folder, Control-V (paste)
You can now install SQL Server. Note: You will have to re-link any previously existing databases from the DATA_OLD folder.

SSIS Packages and TFS post-merge-script?

I'm running packages on the sql-server from the filesystem.
Now we want to integrade tfs as a version control.
So basically the foldero n the server containing the packages has to be identical to the release-branch in the tfs.
Is there any way to e.g. copy the files on merge to the server?
So basically:
Release-> Branch to Dev -> Edit Packages -> Merge to Release ->Copy Packages from TFS to destination
Is it possible to add a "post-merge-script" that copies the files?
Thank you
After you check in the packages/files to TFS, it will be easy to get them to a workspace.
You can create a workspace on your destination machine, then perform downloading (getting) files from the Server in VS, or use Get command to get the packages/files.

How do i use an SQL query to determine TFS Area name and build path including file name for installers

I am trying to automate the release process associated with installers that have been created on my build server. To do this I was hoping to be able to use an SQL query to get the drop path of the installer including the file name.
In TFS when I go to "Build" and select "Artifacts" I can then use the "Explore" link to get the root path for the build. The subsequent folders "Installer\Disk" path is part of the configuration. However, the actual setup file is composed of the + " setup.exe". Since there are multiple projects in our TFS I was hoping to use a query to find all builds that have a build quality set to "Release" and dynamically find the installer on disk.
Generally our installer names are made up of the root area path name with all text removed. I can't figure out how to connect the build to the root area path in SQL.
Any ideas?
Generally, Accessing the information from Database directly is not recommended since it is in a high risk. I would recommend you to use TFS API to do this.
The drop location of the build is stored in TFS Collection Database\tbl_Build table and the quality information is stored in tbl_BuildQuality table. Join these two tables to query the information you want.

Where to place database files in Visual Studio

If this question has been asked before please point me in the right direction.
I am working with an MDF file which I attach to localdb in Visual Studio.
However, when I run my application it is copied to the Debug folder (I know this is because the "Copy always" option is set)
This works fine because my connection string is:
Data Source=(localdb)\v11.0;AttachDbFilename=|DataDirectory|\Invoicing.mdf;Integrated Security=True
which means my application will look for the database in the Debug folder.
My question is, where should I place the database file because :
1. The file I am attaching to localdb is under the projects folder
2. Meanwhile, my application looks for the database file in the debug folder
I would appreciate any guidelines
I found this article:
http://msdn.microsoft.com/en-us/library/ms246989.aspx
I guess I will have to attach the one in the bin folder and choose the option to copy if newer
EDIT:
I have done the above and in addition I have created two connections, one for the MDF in the projects folder and the other to view data in the database in the bin folder

Resources