|
|
Posted by Hugo Kornelis on 09/25/06 23:04
On 25 Sep 2006 12:13:23 -0700, tlyczko wrote:
>I am new to SS2005, and I've just started working on a small test/dev
>database.
>
>I recently read that one should store things like tables, views,
>constraints, etc. in the *.ndf file rather than in the *.mdf file.
>
>Does this make it any easier to transfer/copy files or databases or
>other items from test/dev to production??
>
>If I have a database already with items in the *.mdf file, how do I
>transfer things like tables, constraints, views, etc. to an *.ndf file
>in another database??
>
>I also read that one can make it the default in SS2005 to store things
>in the *.ndf file, how is this done??
>
>Thank you,
>Tom
Hi Tom,
I'd like to know where you've read this nonsense. For starters, views
and constraints are only stored as metadata. And even for tables, this
is an incorrect general rule.
Very experienced DBAs will sometimes use different filegroups, placed on
seperate spindles, either to tweak performance or to facilitate advanced
backup and recovery schemes for large DBs. This kind of tweaking is not
of the "all tables go to the *.ndf file (the second filegroup)" kind -
indeed, it involves carefully planning the location of each individual
object, based on typical usage patterns.
Beginning DBAs shouldn't worry about this. For now, making sure to place
your datafile (.mdf) on one spindle and the log file (.ldf) on another
spindle is a good start. Worry about diifferent filegroups when you have
plenty of experience and read and experimented enough to know what the
consequences of using different filegroups are.
--
Hugo Kornelis, SQL Server MVP
Navigation:
[Reply to this message]
|