|
|
| Time Generated: |
2005/11/12 16:40:00 |
| Date Imported: |
2005/11/09 12:25:59 |
| Repository Location: |
//TsaSdSvr2/C-Drive/VssTest2 |
Blank fields = N/A
| Summary |
Action
Purge
Projects |
Action
Purge
Project Files |
Action
Replace |
Action
Replace & Pin |
Action
Review |
Projects Affected |
Files Purged
or Purgeable |
Manual
User
Time |
PC
Time |
Auto
User
Time |
| Purge Projects |
387(10.8%) |
6872(10.1%) |
|
|
|
|
4428(14.3%) |
4:36:19 |
0:18:58 |
0:00:20 |
| Purge Project Files |
|
2621( 3.9%) |
|
|
|
362(10.1%) |
953( 3.1%) |
4:15:44 |
0:42:06 |
0:00:03 |
| Dupe File Names |
|
|
906( 2.9%) |
532( 1.7%) |
681( 2.2%) |
405(11.3%) |
1438( 4.7%) |
28:36:50 |
1:35:22 |
0:14:54 |
| Branched Files |
|
|
125( 0.4%) |
116( 0.4%) |
84( 0.3%) |
118( 3.3%) |
241( 0.8%) |
10:34:00 |
0:37:04 |
0:01:58 |
| Totals |
387(10.8%) |
9493(14.0%) |
1031( 3.3%) |
648( 2.1%) |
765( 2.5%) |
885(24.7%) |
7060(22.9%) |
48:02:54 |
3:13:31 |
0:17:18 |
Upon completion of these actions, you will have:
- Removed 387 deleted projects, reducing your project count by 10.8%
- Removed 9493 deleted project files, reducing your project file count by 14.0%
- Removed 7060 files that have no active links, reducing your file count by 22.9%
- Identified and replaced 1031 duplicate files (evil twins) or inapproprately branched files.
These replace files will have no active links and when they are purged, will reduce your file count by 3.3%
- Identified and Replace & Pin'd 648 duplicate files (evil twins) or inapproprately branched files.
These replace files will have no active links and when they are purged, will reduce your file count by 2.1%
- Identified for further review 765 near duplicate files (evil twins) or inapproprately branched files.
If Replace or Replace & Pin actions are taken and subsequent purge performed, this will reduce your file count by 2.5%
Summary:
- Reduce Projects by 387 or 10.8%
- Reduce Project Files by 9493 or 14.0%
- Reduce Files by 8739 or 28.3%
| Purged Projects |
Number of projects that will be purged. |
| Purged Project Files |
Number of project files that will be purged. |
| Projects Affected by Purge |
Number of projects that are affected by the purged project files.These remain active projects. This number is provided as an indicator of how far-reaching the purge may be. |
| Files Affected by Purge |
Number of files that are affected by the purged project files.This number is provided as an indicator of how far-reaching the purge may be. If all links are purged, VSS will remove the file. If link count becomes 1, then file will no longer be shared. |
| |
|
| Manual User Time |
Estimated time user must remain involved in performing the indicated actions manually. Due to typical interruptions, this should be viewed as a minimum time. |
| PC Time |
Estimated time that the actual processing will take. This time is included in the Manual User Time, but excluded from the Auto User Time. This is because once a user begins the SSAnalyzer (Auto) process, the user can then focus on other tasks. |
| Auto User Time |
Estimated time a user will dedicate in using SSAnalyzer to identify and select actions to be performed. This is a best-case number that assumes the user will accept all the recommendations made by SSAnalyzer. |
| |
|
| Note 1 |
Action percentages are percentage of Total Files |
| Totals |
Found |
Imported |
Orphans |
Current
Total |
Current
Active |
File
History
Only |
Current
Inactive |
| Projects |
3730 |
3580 |
150( 4.2%) |
3580 |
3193 |
|
387(10.8%) |
| Files |
32161 |
30880 |
1281( 4.1%) |
30880 |
24363 |
1136 |
5381(17.4%) |
| Project Files |
69333 |
67868 |
1465( 2.2%) |
67868 |
58375 |
|
9493(14.0%) |
| Found |
Number of items found during import |
| Imported |
Number of items imported |
| Orphans |
Number of items that cannot be accessed via VSS |
| Current Total |
Number of items that currently exist. Any difference from Imported indicates changes have been made using SSAnalyzer. |
| Current Active |
Number of items that are not deleted or in deleted projects. |
| Current Inactive |
Number of items that are deleted or in deleted projects. |
| File History Only |
Number of files that exist only because they are required for Branch history. They are not directly used in any project. |
| |
|
| Note 1: |
Orphan percentages are percentage of Imported items |
| Note 2: |
Current Inactive percentages are percentage of Current Total items |
| Orphan Items |
Count |
| Potentially orphaned Projects |
150( 4.2%) |
| Potentially orphaned Files |
1281( 4.1%) |
| Potentially orphaned Project Files |
1465( 2.2%) |
| Benefit 1 |
Removing orphaned projects and project files will provide incremental speed increases during everyday VSS use and reduce run-times for Analyze.exe and VssDataWiz.Exe. |
| |
|
| Note 1 |
Microsoft describes orphans as items left over from a failed delete/purge action. |
| Note 2 |
Use the Microsoft utility VssDataWiz to specificly identify and fix these items. |
| Note 3 |
You do not need SSAnalyzer to identify orhpans. The Microsoft utility VssDataWiz will this. |
| Note 4 |
Estimated run times for use of VssDataWiz depend on size and condition of VSS repository. |
| Note 5 |
Orphan percentages are percentage of Imported items. |
| Unpurged Projects |
Count |
Removed from VSS |
No longer shared |
Remain as shared |
Manual
Time
per Item
(secs) |
Auto
Time
per Item
(secs) |
Manual
Time |
Auto
Time |
| Projects |
133( 3.7%) |
|
|
|
40.0 |
0.1 |
1:28:40 |
0:00:13 |
| Sub Projects |
254( 7.1%) |
|
|
|
40.0 |
0.1 |
2:49:20 |
0:00:25 |
| Project Files |
6872(10.1%) |
4524( 6.7%) |
232( 0.3%) |
1326( 2.0%) |
0.2 |
0.2 |
0:18:19 |
0:18:19 |
| Files |
5514(17.9%) |
4428(14.3%) |
242( 0.8%) |
287( 0.9%) |
|
|
|
|
| Total |
|
|
|
|
|
|
4:36:19 |
0:18:58 |
| Benefit 1 |
Purging Projects and Project Files reduces the number links to shared files. This speeds up most VSS actions on the shared files. |
| Benefit 2 |
When link count equals 0, VSS will remove the unreferenced file. This results in a smaller VSS repository and increasing the accuracy of 3rd-party reporting. |
| |
|
| Note 1 |
Manual Project/SubProject per item estimates are the time it takes to navigate to each project using the VSS GUI, select properties, and Purge entries. |
| Unpurged Project Files |
Count |
Removed from VSS |
No longer shared |
Remain as shared |
Manual
Time
per Item
(secs) |
Auto
Time
per Item
(secs) |
Manual
Time |
Auto
Time |
| Projects |
362(10.1%) |
|
|
|
40.0 |
0.1 |
4:01:20 |
0:00:36 |
| Project Files |
2621( 3.9%) |
1152( 1.7%) |
161( 0.2%) |
1308( 1.9%) |
0.3 |
0.9 |
0:14:24 |
0:41:29 |
| Files |
1713( 5.5%) |
953( 3.1%) |
130( 0.4%) |
182( 0.6%) |
|
|
|
|
| Total |
|
|
|
|
|
|
4:15:44 |
0:42:06 |
| Benefit 1 |
Purging Projects and Project Files reduces the number links to shared files. This speeds up most VSS actions on the shared files. |
| Benefit 2 |
When link count equals 0, VSS will remove the unreferenced file. This results in a smaller VSS repository and increasing the accuracy of 3rd-party reporting. |
| |
|
| Note 1 |
Manual Project/SubProject per item estimates are the time it takes to navigate to each project using the VSS GUI, select properties, and Purge entries. |
| Dupe File Names |
Count |
Sig
Count |
NonSig
Count |
Affected
Projs |
Affected
ProjFiles |
Manual
Time
per Item
(secs) |
Auto
Time
per Item
(secs) |
Manual
Time |
Auto
Time |
| Unique File Names |
3908(12.7%) |
2336( 7.6%) |
1572( 5.1%) |
|
|
|
|
|
|
| Unique Files |
7732(25.0%) |
6493(21.0%) |
1239( 4.0%) |
|
|
|
|
|
|
| Action - Replace |
|
906( 2.9%) |
|
307 |
1398 |
35.0 |
2.1 |
17:00:10 |
0:49:26 |
| Action - Pin |
|
532( 1.7%) |
|
222 |
947 |
40.0 |
2.9 |
12:59:20 |
0:46:08 |
| Action - Review |
|
681( 2.2%) |
|
312 |
1011 |
|
|
|
|
| Action - TOTAL |
|
2119( 6.9%) |
|
405 |
2345 |
|
|
28:36:50 |
1:35:22 |
| Benefit 1 |
Identifies files which may have been copied and added to a project rather than shared. This less-than-best practice eliminates the advantage of sharing a file and typically causes confusion as to which file is the true file to be shared. |
| Benefit 2 |
Identifies users who may be using less-than-best practices when using VSS. This provides an opportunity to conducte some very simple and direct training to eliminate these less-than-best practices in the future. |
| |
|
| Unique File Names |
Number of unique file names when the number of files with the same name > 1. |
| Unique Files |
Within the list of Unique File Names, the number of unique ( or physical) files. |
| NonSignificant File Names |
Within the list of Unique File Names, the number of Unique File Names that have 1 or fewer Unique Files that have Active (undeleted) links <= 1. Typically, these Duplicate File Names disappear after Unpurged Project and Unpurged Project Files is completed. |
| Significant File Names |
Within the list of Unique File Names, the number of Unique File Names that have 2 or more Unique Files that have Active (undeleted) links > 1. SSAnalyzer Dupe File Name option identifies recommended actions to correct these problems. |
| |
|
| Action - Replace |
SSAnalyzer was able to identify files where latest versions of each are effective duplicates and recommends the replacement of one file with the other. |
| Action - Replace& Pin |
SSAnalyzer was able to identify files where latest versions of one is an effective duplicate of a non-latest version of another. SSAnalyzer recommends the replacment one file with the other and pinning at the matched verions until a manual review can be performed to determine if unpinning is appropriate. |
| Action - Review |
SSAnalyzer found two related files (FileName or Branch) that matched very closely. Typically a manual review of these files indicates that one file can be replaced by the other, or perhaps they should be merged and then projects adjusted. |
| Action - TOTAL |
Affected Projects, Manual Time and Auto Time may be less than sum. This is due to projects that may require more than one Action (Replace, Pin, Review), but a single navigation. |
| |
|
| Note 1 |
Manual per item estimates are the time it takes to navigate to each project using the VSS GUI and then executing the specified action. Automatic estimates do not include the navigation time. |
| Note 2 |
It is important to recognize that the manual time requires the user's constant attention in order to navigate to the next project/action. The automatic time is how long SSAnalzyer will be running while the user is free to perform other tasks. |
| Branched Files |
Count |
Sig
Count |
NonSig
Count |
Affected
Projs |
Affected
ProjFiles |
Manual
Time
per Item
(secs) |
Auto
Time
per Item
(secs) |
Manual
Time |
Auto
Time |
| Root |
1024( 3.3%) |
379( 1.2%) |
645( 2.1%) |
|
|
|
|
|
|
| Branch |
1157( 3.7%) |
53( 0.2%) |
1104( 3.6%) |
|
|
|
|
|
|
| Rollback |
851( 2.8%) |
531( 1.7%) |
320( 1.0%) |
|
|
|
|
|
|
| Action - Replace |
|
125( 0.4%) |
|
73 |
464 |
35.0 |
2.1 |
5:19:20 |
0:16:21 |
| Action - Pin |
|
116( 0.4%) |
|
86 |
427 |
40.0 |
2.9 |
5:42:00 |
0:20:46 |
| Action - Review |
|
84( 0.3%) |
|
75 |
141 |
|
|
|
|
| Action - TOTAL |
|
325( 1.1%) |
|
118 |
891 |
|
|
10:34:00 |
0:37:04 |
| Benefit 1 |
Identifies files which may have been copied and added to a project rather than shared. This less-than-best practice eliminates the advantage of sharing a file and typically causes confusion as to which file is the true file to be shared. |
| Benefit 2 |
Identifies users who may be using less-than-best practices when using VSS. This provides an opportunity to conducte some very simple and direct training to eliminate these less-than-best practices in the future. |
| Root |
Number of unique (or physical) files that were created with a VSS Add/Create action. |
| Branch |
Number of unique (or physical) files that were created with a VSS Branch action. |
| Rollback |
Number of unique (or physical) files that were created with a VSS Rollback action. |
| |
|
| Unique Files |
Within the list of Unique File Names, the number of unique ( or physical) files. |
| NonSignificant File Names |
Within the list of Unique File Names, the number of Unique File Names that have 1 or fewer Unique Files that have Active (undeleted) links <= 1. Typically, these Duplicate File Names disappear after Unpurged Project and Unpurged Project Files is completed. |
| Significant File Names |
Within the list of Unique File Names, the number of Unique File Names that have 2 or more Unique Files that have Active (undeleted) links > 1. SSAnalyzer Dupe File Name option identifies recommended actions to correct these problems. |
| |
|
| Action - Replace |
SSAnalyzer was able to identify files where latest versions of each are effective duplicates and recommends the replacement of one file with the other. |
| Action - Replace& Pin |
SSAnalyzer was able to identify files where latest versions of one is an effective duplicate of a non-latest version of another. SSAnalyzer recommends the replacment one file with the other and pinning at the matched verions until a manual review can be performed to determine if unpinning is appropriate. |
| Action - Review |
SSAnalyzer found two related files (FileName or Branch) that matched very closely. Typically a manual review of these files indicates that one file can be replaced by the other, or perhaps they should be merged and then projects adjusted. |
| Action - TOTAL |
Affected Projects, Manual Time and Auto Time may be less than sum. This is due to projects that may require more than one Action (Replace, Pin, Review), but a single navigation. |
| |
|
| Note 1 |
Manual per item estimates are the time it takes to navigate to each project using the VSS GUI and then executing the specified action. Automatic estimates do not include the navigation time. |
| Note 2 |
It is important to recognize that the manual time requires the user's constant attention in order to navigate to the next project/action. The automatic time is how long SSAnalzyer will be running while the user is free to perform other tasks. |
|
|