All geek questions in one place

Why do I need secondary data files in SQL Server?

I always ignore this option when creating a new database on SQL Server 2005, simply because we can ignore what we don’t understand and leave it as it is. (I'm not in DBA)

So now I wonder what that means.

From your experience, when, in your opinion, we need to add secondary information files to my database and why do we need it?

+3
source share
3 answers

There are many cases where this can be useful - for starters, for reasons of accessibility, it is always better to store only system data in your main data file (with Sql2k5 and higher, if the main data file is available, the database can be connected to the network, allowing you to restore / restore / etc. non-system data, having as many online features as possible). Some other uses of secondary files:

  • Splitting data across multiple LUNs
  • Allow partial / backup / restore filegroups
  • Segmenting different types of read / write accesses on different LUNs (e.g. sequential or random)
+3
source

, , .

( , , ) , .

, , , , , , .

( ) , - .

, , , .

+1

One of the main reasons is I / O. Being able to split your data means that I / O now extends to multiple drives / luns / etc. which can significantly increase productivity.

0
source

Source: https://habr.com/ru/post/1722438/

More articles:


All Articles