Database size

  • Put brackets around it like this:

    ALTER DATABASE Claims

    ADD FILE

    ( NAME = Claims_dat2,

      FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL$SQLSERVER2000\Data\Claims2.mdf',

      SIZE = 5GB,

     MAXSIZE = 10GB,

     FILEGROWTH = 1 GB)

    TO FILEGROUP [PRIMARY]

    You will get an error if you try to make the file size 5GB, it must be less than 4GB.  I'd suggest creating a couple new data files with a max size of 4GB (or less) and not let them grow.

    Hope this helps.

    Jarret

  • Try it without the "TO FILEGROUP PRIMARY"

    And if you haven't converted to NTFS then the initial and max sizes need to be below 4GB.

      SIZE = 5GB,
     MAXSIZE = 10GB,
     FILEGROWTH = 1 GB 

    Why don't you convert to NTFS?



    ----------------
    Jim P.

    A little bit of this and a little byte of that can cause bloatware.

  • Thank you both - I have SQL Server loaded locally on my machine - to get some work done before the server arrived and was just a stop gap option. Would converting to NTFS make me lose my data on my hardd dirve is I do it using the cmd prompt?

  • It shouldn't.

    I would see if there was a way to back up the system before conversion. I've converted over several systems to NTFS without a problem.

    http://www.ntfs.com/quest3.htm

    http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/convertfat.mspx

    http://www.tweakxp.com/tweak264.aspx



    ----------------
    Jim P.

    A little bit of this and a little byte of that can cause bloatware.

  • I'm suprised how anything didn't go wrong till now!

    Run (chkdsk c: /r /p) before converting

    then convert

    Yes, you will loose with converting, and what you will loose will be problems.

    I had converted tens of volumes, and I had once problems, but it was solved with chkdsk c: /r /p

    So, do it, or stay with problem

Viewing 5 posts - 16 through 19 (of 19 total)

You must be logged in to reply to this topic. Login to reply