New SQL Server 2000 installation
Steve M.
I'm going to be setting up a new SQL server and was hoping to get some
recommendations (tips and best practices) because I've never installed SQL
server before.
The server I have for the project is a Dell PE1850: single 3GHz Xeon, 1GB
RAM, 36GB hard drive capacity (hardware RAID 1). It will run Windows 2003
Server Standard edition.
We have a separate IIS server that will host the websites using this SQL
server.
I found Microsoft's "10 Steps to Help Secure SQL Server 2000" and an article
on TechRepublic called "Install SQL Server 2000 for optimal usability." Can
anyone recommend any other resources or make any setup suggestions based on
your own experiences?
Also, I have a specific question:
How should I partition the drives for administration purposes? (I know there
won't be a performance improvement with partitioning since I'm doing RAID
1.)
Thanks,
Steve
Andrew J. Kelly
If you do then you always run the risk of running out of disk space on one
partition or the other. If it is all one large partition then you get
maximum flexibility and you don't give someone the false impression you have
more than one physical drive.
--
Andrew J. Kelly SQL MVP
"Steve M." <maj...@cox.net> wrote in message
news:O6sO0ljZ...@TK2MSFTNGP14.phx.gbl...
Steve M.
Gateway desktop - eeks), has only 4 gigs in use total. That's OS, SQL server
and data combined. We're not a huge scale operation and I don't anticipate
much growth during the life (3-4 yrs) of this server.
That said, what kind of strategy would you use for separating things with
partitions?
- Steve
"Leythos" <vo...@nowhere.lan> wrote in message
news:MPG.1d06cea5f...@news-server.columbus.rr.com...
> In article <#$r8dBkZF...@tk2msftngp13.phx.gbl>,
> sqlmvpn...@shadhawk.com says...
>> I recommend you don't partition it at all other than one large partition.
>> If you do then you always run the risk of running out of disk space on
>> one
>> partition or the other. If it is all one large partition then you get
>> maximum flexibility and you don't give someone the false impression you
>> have
>> more than one physical drive.
>
> With his small drive I will have to agree with you, 36GB is just small
> in any server. Running with two partitions is safer and permits more
> flexibility when it comes to security and also to management of files
> space and fragmentation.
>
> Increasing a partition size on a single disk is simple when moving to a
> new disk - Ghost permits resizing partitions when moving between
> physical disks.
>
> --
> --
> spam9...@rrohio.com
> remove 999 in order to email me
Hank Arnold
will only need 1GB. Remember, the OS has to share that memory....
You *really* should have another physical drive. It's not a great idea to
run the program and the database files and transaction logs all on one
drive. If that's not going to happen, then, I defer to the experts on
whether you should use a single partition or two. My inclination would be
for two, but I'm definitely not an expert....
--
Regards,
Hank Arnold
"Steve M." <maj...@cox.net> wrote in message
news:O6sO0ljZ...@TK2MSFTNGP14.phx.gbl...
Steve M.
Thanks for the reply. Right now we're running SQL on a Gateway desktop with
a single IDE drive and 512MB RAM -- and don't have any performance issues.
It's a scary setup for a number of reasons, but it actually works just fine.
The PE1850 only holds two drives, so I'm stuck with a mirrored SCSI
configuration. (You have to admit that's much better than a single IDE!)
- Steve
"Hank Arnold" <ras...@aol.com> wrote in message
news:u6PKhKoZ...@TK2MSFTNGP09.phx.gbl...
Gordo
SQL separately on another larger partition. Makes it a bit easier to
manage the SQL installation. It's also a good idea to separate the
database installation so you can provide for specific security
permissions for the SQL Administrators and developers without impacting
the OS installation.