Hello,
I may come across a strange situation while migrating TFS 2010 to TFS 2013 in nearby future i.e.
1. I have a SAN disk which has a maximum capacity of 500GB and it doesn't allow me to extend beyond as per standards.
2. There are three(3) collections in a Clustered SQL Server 2008 R2 instance on Win 2008 R2 EE.
3. First collection occupies ~250 GB, Second collection ~190 GB, Third collection ~ 10GB and the remaining 50 GB is distributed among databases like Sharepoint products, ReportServer, Tfs_Warehouse.
4. Due to lots of Dev work, the disk space is nearing 500 GB.
5. We know that we can add and map a new disk drive to existing 3 collections (from Database Properties > Files > Add and map new disk drive > Click Ok, the work is done.
6. Currently the 3 collections are mapped to a particular drive (D:\DATA), now if we add another drive and map it to all 3 collections in same/another drive say (D:\DATA1), so whatever the action (check-in, builds data, Work items triggers on VC), the data will get stored in (D:\DATA1) remember it's DATA1.
7. The Situation here is in the next 6 months at any time we migrate the TFS from 2010 to 2013 and not sure of any dates yet.
8. From this situation if data gets stored on second disk i.e. D:\DATA1, so we will get 2 (.mdf files) here.
9. So, how will it impact when we migrate TFS 2010 to 2013 having 2 (.mdf files). Will migration be successfull??
10. Or Should we find alternatives like Shrinking/Purging or Restrict Autogrowth properties for Collection databases.
Note: BTW, let me remind -> we don't and not in a position to Split the Collection.
Please provide your valuable experience and can send me the information on my signature mail id as well. Thanks a lot in advance.
Regards,
Vinod Kulkarni