January 6, 2010 at 1:29 pm
We have a SQL2005 database that's about 93GB, using only the primary datafile. We are not having any performance issue but should we create a secondary datafile or is this not needed? Thanks.
January 6, 2010 at 1:33 pm
If the data is static (won't be modified) than why not?
If you don't query that data a lot, then move it to a cheaper storage and use current storage for something more important.
You can alter the backup process and take backup of static data once a week and backup more recent data more often.
January 6, 2010 at 2:11 pm
Have a read of Tony Robinson's blog post here, it may help you answer your question:
http://sqlblogcasts.com/blogs/tonyrogerson/archive/2006/08/17/948.aspx
Gethyn Elliswww.gethynellis.com
January 6, 2010 at 2:17 pm
If the data is static and I add a secondary data file, won't SQL try to automatically balance the two data files? Thanks.
January 6, 2010 at 2:35 pm
not if it is added as a file in a new filegroup
---------------------------------------------------------------------
January 6, 2010 at 3:19 pm
Before you go off and start creating multiple files - read this:
http://blogs.msdn.com/psssql/archive/2007/02/21/sql-server-urban-legends-discussed.aspx
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply