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 |
|
AjarnMark
SQL Slashing Gunting Master
3246 Posts |
 Posted - 2001-08-20 : 18:24:23
|
| We have a "development" SQL Server (SQL 7, NT 4) with a 20 GB drive and 512MB RAM. Our "production" SQL Server is SQL 7, NT 4, 28GB drive, 580MB RAM. We tend to have a lot of smaller databases because we have multiple departments with their own developers, and we also have Oracle database servers for the biggest apps.I understand that ideally, we would do analysis on actual expected rowsizes and tablesizes analysis, but it's just not going to happen from many of these departments. Does anybody have a recommendation for a nice "default" MaxSize that I can implement and change later as need-be? What other recommendations are there for setting MaxSize on the databases for either dev or production? What about MaxSize for the Logs? And will changing the MaxSize on the Model database then cause those limits to be used as default values for any new databases?Thanks!------------------------------------------------------------------Contractor$ never die, they just leave for higher-paying project$.Edited by - AjarnMark on 08/20/2001 18:25:14 |
|
|
|
|
|
Database MaxSize Recommendations