Yes. Just because is probably the best answer. It has to do with the way the db structure is laid out originally. If you were to reduce the database on the original system before you do the backup, then you could restore into a smaller database...
Kelly J. Lipp VP Manufacturing & CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 [EMAIL PROTECTED] -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Tim Brown Sent: Wednesday, December 12, 2007 12:48 PM To: [email protected] Subject: [ADSM-L] DB size for recovery purposes Have DB with size of 31,440 MB. Attempting to load a copy of the database on my recovery system. DB is 53% full. Available Assigned Maximum Maximum Page Total Used Pct Max. Space Capacity Extension Reduction Size Usable Pages Util Pct (MB) (MB) (MB) (MB) (bytes) Pages Util --------- -------- --------- --------- ------- --------- --------- ----- ----- 31,440 31,328 112 3,432 4,096 8,019,968 4,275,204 53.3 53.5 I didn't create the recovery DB with the same capacity since the actual one is only just over half utilized. The error I get when loading the recovery DB is Database capacity required for restore is 31328 megabytes. Database available capacity is 18864 megabytes. Does the recovery db have to be the same size even though its not fully utilized. If the answer is yes why ? Tim Brown Systems Specialist - Project Leader Central Hudson Gas & Electric 284 South Ave Poughkeepsie, NY 12601 Email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Phone: 845-486-5643 Fax: 845-486-5921 Cell: 845-235-4255
