Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
coreysan
Starting Member
13 Posts |
 Posted - 2011-03-02 : 12:59:45
|
| I was given a DB about 15 gigs in size, all of it on one MDF, and oneldf file. The tables are heavily populated with calculated fields as well, and there are lots of views. I'd like to see if I can redesign the DB by adding filegroups, placing them on different partitions, and separating the indices to different filegroups as well, but I don't know enough about SQL Server to know if it can be done without first dumping all the data, and then re-loading. Can it be done on the fly? For example, if I added a new filegroup to the DB, how would I move the data from the single mdf chunk to the new filegroup... or am I required to dump/load?Thanks for any response at all!Corey |
|
|
X002548
Not Just a Number
15586 Posts |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
coreysan
Starting Member
13 Posts |
Posted - 2011-03-04 : 13:25:23
|
| tkizer,So you think that maybe a 15 gig file wouldn't require filegroups? In my opinion, the IO seems to be really poor. I realize that some of it is the nature of the DB, and it requires optimization, but Iwondered if filegroups would help. If it wouldn't make much of a change, then of course I don't want to do all that extra work.Is bcp the best practice, or alter database? |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|
|
|
|
Can I resign a DB without dump/loading?