MDF's more than one on a database

  • Hi All,

    I have some third party applications like geophysics ones, that runs with SQL database. When this apps were installed in our servers automatically creates its own database structure, however since then no one does any mantenaince to that server, now that MDF and LDF files are full...I can run a shrinkfile to the log file so I can "clean" it up a little, but the MDF is about 10GB. Can I create a new NDF file without causing the application stop working correctly?....I know I can do it, but how the application will know that has to grab this NDF file??

    I need some advise.

    Thank you in advance.

  • Junior_DBA (4/30/2009)


    Hi All,

    I have some third party applications like geophysics ones, that runs with SQL database. When this apps were installed in our servers automatically creates its own database structure, however since then no one does any mantenaince to that server, now that MDF and LDF files are full...I can run a shrinkfile to the log file so I can "clean" it up a little, but the MDF is about 10GB. Can I create a new NDF file without causing the application stop working correctly?....I know I can do it, but how the application will know that has to grab this NDF file??

    I need some advise.

    Thank you in advance.

    You can add a second data file (wth the default NDF extension), but it won't be used until you actually move some of the structures onto that file / filegroup. Most likely, the company providing you with the application would prefer that you let them handle that type of thing. I'd contact them, let them know your concerns, see what they have to say.

  • The below article takes u step by step towards moving data to a different file group and answers your question about how your data will start moving to new file group:

    http://www.sqlservercentral.com/articles/Administration/64275/

  • The addition of a file to the existing file group (PRIMARY) is all you need to do. SQL Server will automatically start using it. The application does not know anything about this.

    If you happen to add the new file to a different file group (which you would need to create), you would also need to move tables or indexes to it. This would require you (or the vendor) to get involved.

    If the only reason for adding a new file is to add more space to the database, I would use the PRIMARY file group and let SQL Server sort it out.

  • All you need to do is change the maximum file size on the mdf and ldf files... that is unless your volume where those files reside is full. If the disk is full you should mention that in your post to get the appropriate advice

    Cheers!

    ~BOT

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

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