TFS数据库升级到2017年重新编制索引 [英] TFS Database upgrade to 2017 Re-indexing

查看:70
本文介绍了TFS数据库升级到2017年重新编制索引的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个耗费370GBS磁盘空间的TFS 2012 Update 2数据库。我已经设法清除了288GB,主要包括已删除版本的构建信息,TestResults和FunctionCoverage,留下了很多可回收的空间,我想为其他目的提供


我相信(从我所读到的)缩小数据库文件会使索引碎片化,我认为这会影响性能。


第一个问题:缩小TFS数据库是否会产生重大影响关于性能?


第二个问题:TFS 2017安装执行的数据库升级是否会重建索引?


谢谢


Sj

解决方案

嗨Sj,


感谢您在此发帖。


关于第一个问题,缩小TFS数据库不会对性能产生很大影响。
收缩数据文件通过将数据页从文件末尾移动到靠近文件前面的未占用空间来恢复空间。  收缩操作不会保留
数据库中索引的碎片状态。
关于第二个问题, 我不确定升级是否会重建索引,但缩小不会删除索引。


以防万一,在您收缩之前备份您的数据库。 最好的问候


I have a TFS 2012 Update 2 database consuming 370GBS of disk space. I have managed to clear 288GBs ,consisting mainly of build information, TestResults and FunctionCoverage for deleted builds, leaving alot of reclaimable space which I would like to provision for other purposes.

I believe (from what i have read) that shrinking the database file can leave indexes fragmented which I will assume can affect performance.

First question: Is shrinking the TFS database going to have big impact on performance?

Second Question: Does the database upgrade performed by the TFS 2017 installation rebuild the indexes?

Thanks

Sj

解决方案

Hi Sj,

Thank you for posting here.

About the first question, shrinking a TFS database won't have big impact on performance. Shrinking data files recovers space by moving pages of data from the end of the file to unoccupied space closer to the front of the file. A shrink operation does not preserve the fragmentation state of indexes in the database. About the second question, I'm not sure about whether the upgrading will rebuild the index, but the shrinking won't delete the index.

Just in case, backup your databases before you do the shrinking .Best regards


这篇关于TFS数据库升级到2017年重新编制索引的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆