|
Home > Archive > MS SQL Server > March 2006 > Organizing file groups for multiple databases
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Organizing file groups for multiple databases
|
|
| bantar 2006-03-26, 8:23 pm |
| Greetings;
I have a SQL Server installation that has 2 critical production databases
(~8Gb each) and 15-20 test & dev databases ranging from 200Kb to 50Gb. The
prod dbs need to be 100% recoverable, while the test & dev dbs need only
simple non-automated backup & recovery. There are only 2 or 3 disk drives
available, all approx 100Gb. What is the best way to organize file groups,
log files, and backup files in this scenario? Backup to disk is the only
option currently available. RAID is not an option at this time.
TIA
| |
| John Bell 2006-03-26, 8:23 pm |
| Hi
Mixing production, test and development databases on the same server is not
a great idea as problems with test or development may effect production. Even
if you moved the databases onto different drives they will still be competing
for shared resources.
John
"bantar" wrote:
> Greetings;
>
> I have a SQL Server installation that has 2 critical production databases
> (~8Gb each) and 15-20 test & dev databases ranging from 200Kb to 50Gb. The
> prod dbs need to be 100% recoverable, while the test & dev dbs need only
> simple non-automated backup & recovery. There are only 2 or 3 disk drives
> available, all approx 100Gb. What is the best way to organize file groups,
> log files, and backup files in this scenario? Backup to disk is the only
> option currently available. RAID is not an option at this time.
>
> TIA
>
| |
| John Bell 2006-03-27, 3:23 am |
| Hi
WIth the hardware you have, then you can't do alot! If there is only a
couple of developers then you may want to consider purchasing a copy of the
developer edition and put the databases on a development pc to remove those
databases from the equation. As you have ruled out raid you can not add
resiliance through hardware, therefore the best you can do is to make sure
that you have regular and sufficient backups for recovery. You may also want
to look at ghost to make sure that you have an image of the system that can
be recovered. Look at having regular database backups that are copied to a
(one or more) different system reducing the exposure to a hardware failure on
the one system. For disc layout you may want to separate the database file
and log files from the OS, therefore having one drive for each may help.
Backing up the databases onto the OS drive before they are copied to your
alternate location may be another thing you can do.
John
"bantar" wrote:
[color=darkred]
> Thanks for the reply, John. I understand that the configuration is not a
> recommended one... as you can imagine I inherited the role of admin, and the
> system and resources available are what they are for the near term. My
> question is how to best organize what I have now, most importantly to improve
> recoverability of the production dbs.
>
>
> "John Bell" wrote:
>
|
|
|
|
|