SQL을 통해 내 콘텐츠 데이터베이스를 정기적으로 백업하고 축소해야합니까?

Question

SharePoint 2010 (SQL 2008 SQL) 환경에서 하드 디스크 공간이 잠시 동안 경쟁 해왔고 최근에 내가 도움이 될 수있는 몇 가지 사항을 알아 냈습니다.

트랜잭션 로그 백업을 정기적으로 실행 한 다음 내 콘텐츠 데이터베이스를 축소해야합니까?사용 가능한 디스크 공간을 늘리는 데 도움이 될 것입니까?백업 실행을 괴롭히는 데 도움이 필요합니까?

저는 DBA (분명히) 아니지만 SQL에 대해 하나 또는 두 가지 사항을 알고 있으므로 당신의 설명과 함께 그것을 염두에두고있는 시간을 앞두고 있습니다.:)

Answer 1

You should be backing up and truncating your TLOGS. If you have not been doing that, than yes, do a backup, truncate, and shrink will restore space. To keep that space however, you will need to set growth limits on your database and log files. Microsoft has a paper on "best practices" with SQL maintenance:

http://technet.microsoft.com/en-us/library/cc262731.aspx

While I recomend you run thru that whitepaper, I suggest you look at bigger drives to support your installation, they are cheap, and it is worth the front loaded effort to make that swap rather than chasing down a few MB here and there.

Answer 2

First thing you should do is choose the appropriate recovery model for your databases.

If you need point in time restore, go for the FULL recovery model. The price you have to pay is to make regular log backups or your logfile will grow indefinitely. Taking a full backup does not stop them from growing. If you use mirroring or log shipping, you also need to be in the FULL recovery model. So you need to take full (or differential) & logs backups.

If you don't need point in time restores - go with the SIMPLE recovery model. SQL Server will automatically manage your transaction log files and reuse them so they don't grow as big. Full (or differential) backups will do just fine in this case.

Shrinking database files should only be done in very specific circumstances (NEVER automatically or as part of a maintenance plan) because they cause horrible fragmentation of your databases. A good candidate is the situation where you just moved a large site collection to another content database and you leave your original database with 80% of unused space for example. Database files grow, that's what they do.