By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,586 Members | 2,418 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,586 IT Pros & Developers. It's quick & easy.

budgeting for a new database?

P: n/a
We're preparing budgets and plans that involve me getting
1-2TB (usable) of disk sometime around October 2005. Currently
we have a shark (ESS). I want to have not only the new server
on the new disk, but also move all my current local disk to
this same (or similiar) device. Since we budgeting for 1-2TB,
we can easily add another 300GB for replacing my local disk.

This new box will be a duplicate DB2 database fed from the
mainframe. It will be used for data warehouse/data mining
applications. Eventually I want to also consolidate *many*
MS SQL databases on Windows servers back into using this
data rather than maintaining their own database instances.

- for the initial application I expect a lot of I/Os
- I want the current local disks on this device for booting
and the applications
- I want to consolidate other databases back into this instance
- I need 1-2TB initially of usable space, though it could grow
to 3-4TB
- I want it through fiber/SAN to make my disaster recovery
scenarios easier

Ok, so opinions on what I should ask for?

Nov 12 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.