Small mdf file, large ndf file

  • Hi

    I've noticed that we have a mdf file with the size off 117 Mb and a ndf file with the size off 22Gb.

    Does this lead to performance issues ?

    If yes how to obtain one file again ?

    Kind regards

    Jeffrey


    JV

  • Generally 2 files are created to improve performance by spreading the data onto multiple disks or arrays. Or it can be done because of space limits on a drive and wanting to make use of another drive.

    If the 2 files are in the same file group, then SQL will control where the data goes, unless one file is full. If the 2 files are in different file groups, then you control which file group tables are in.

    Does the small .mdf have growth limits ?

  • jvElecenter (1/26/2010)


    Does this lead to performance issues ?

    Not by itself, no.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Hi

    See attach.

    There is no restriction in growth.

    Should i take some action ?


    JV

  • Better specify autogrowth in multiple of MB's rather than in terms of percentage.

    MJ

  • might want to check if certain tables are being specifically built on your secondary filegroup.

    this should work:

    SELECT DISTINCT

    OBJECT_SCHEMA_NAME(ID) [SCHEMANAME]

    ,OBJECT_NAME(id) [TABLENAME]

    ,FILEGROUP_NAME(groupid) AS [FILEGROUPNAME]

    FROM SYS.SYSINDEXES

    WHERE OBJECT_SCHEMA_NAME(id) NOT LIKE 'sys%'

Viewing 6 posts - 1 through 5 (of 5 total)

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