November 19, 2003 at 2:58 pm
I am moving a very fragmented db from one server to a new server. I can create a shell<bigger> in the new server but when I restore the db on it, db shows actual db size. My thinking was to create a bigger shell so fragmentations will be minimal. Your opinion?
November 19, 2003 at 3:03 pm
Forgot to put some tech stuff:
Old Server: WinNT. SQL 7.0 Processors: 2 Memory: 3 gb
disk space: ~70 gb Raid 5 db size: ~21 gb (data & log store in the d: drive)
New Server: Win2K, SQL 7.0 (I know, I know.. 3th party app) Procs: 2 Memory 4 gb; Disk Space: 300 gb.Raid 5; db size: ~21 gb (Plan to put Data on D: and Logs on E: drives)
November 24, 2003 at 10:22 am
Shrink the database and rebuild indexes to get rid of fragmentation. If the MDF file itself is fragmented run a defragmentation program when SQL Server is not up. You can't defragment SQL (MDF and LDF) files when SQL Server is running. Usually though rebuilding the indexes does a good job of internally getting rid of fragmentation.
Francis
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply