I have a question regarding Expanding a Native Database. I have just joined a new End User, and their retail database implementation includes a Head Office database, Native Server v3.6. The database is presently ONE file of 132Gb !!! (I know). Database usage is presently at 83%, and growing at 0.3% per day. The plan is to migrate to a new server, with a different and optimal confirguaration within the next 2/3 weeks, so my question is for a short-term, stop gap fix. My IT Director wants a full risk analysis of expanding the current free database space. The options open to me are 1. Expand by adding another file on the same disk (147Gb Free) 2. Expand by adding another file on a different disk (28Gb Free) 3. Deleting old data temporarily (Until new server is implemented) Normally, expanding the database and adding more files would involve backup and restore, but, as the database is in use for almost 20hours per day, this is not necessarily practical. Ideally we wouold create a new database, equal file sizes, different disks etc, but… Can someone advise the potential risks of 1. Expanding the database during the 4 hour period to the same disk 2. Expanding the database during the 4 hour period to a different disk The main reson for the concern is because of issues with restoring into a database larger than 132Gb, although this could possibly have been caused by having different database files, totalling more than 132 Gb, on the same disk. I am not bothered about achieving a performance improvement in the short term - this will come with the new server. I need to ensure that the the current performance will not suffer as a result of a simple expand and addition of a new file. We only need to grab maybe 20Gb to see us through until the new server is implemented, but as this is a retail environment, with back office/head office processes for 20 hours per day, I need to be careful…[Duh!] Cheers, everyone.