It's easier to start a new server and start putting new stuff there,
than it will be to move it later.  Others have indicated reasons why
large databases can be a problem.  I will add to that the time to
audit a database, should you ever find yourself in that unfortunate
situation.  Also unload/reload time, to defragment the database over
time.     ..Paul

At 01:44 PM 10/25/2005, Dearman, Richard wrote:

My TSM database is currently 150GB and I am wondering if I should start
thinking about a second server.  Other than the DB being so large
nothing else is wrong.



Thanks


**************************EMAIL DISCLAIMER***************************

This email and any files transmitted with it may be confidential and are
intended solely for the use of the individual or entity to whom they are
addressed.  If you are not the intended recipient or the individual
responsible for delivering the e-mail to the intended recipient, any
disclosure, copying, distribution or any action taken or omitted to be
taken in reliance on it, is strictly prohibited.  If you have received this
e-mail in error, please delete it and notify the sender or contact Health
Information Management 312.413.4947.

--
Paul Zarnowski                            Ph: 607-255-4757
Manager, Storage Systems                  Fx: 607-255-8521
719 Rhodes Hall, Ithaca, NY 14853-3801    Em: psz1 AT cornell DOT edu