From: Van Messner Subject: Re: dbassist vs create database ? Date: 2000/08/08 Message-ID: <01e5a370.01b7fd06@usw-ex0106-046.remarq.com>#1/1 References: <398ECBA9.8593745A@SPAMwillowglen.ab.ca> <398EDB8B.C59ABDA7@webde-ag.de> <3990120b@news.iprimus.com.au> Bytes: 944 X-Originating-Host: 12.3.14.51 X-Complaints-To: wrenabuse@remarq.com X-Trace: WReNphoon3 965765717 10.0.2.46 (Tue, 08 Aug 2000 13:15:17 PDT) Organization: http://www.remarq.com: The World's Usenet/Discussions Start Here NNTP-Posting-Date: Tue, 08 Aug 2000 13:15:17 PDT Newsgroups: comp.databases.oracle.server X-Wren-Trace: ePXQ+Pngp+2mo+z446b6+fXG4fnj8rr19ev08+iv77r3s+Smteauqq26pKE= I have to disagree with Brad. The new version of dbassist will not create a complete production database. But it will create the framework for one far faster than you can do it by hand in a script. And it will take care of half a dozen or more of those pesky housekeeping chores (unless you LIKE to run catproc.sql by hand and bounce your listener). We create the framework for every production database with dbassist then make the modifications to tablespaces, init.ora parameters etc. right after completion. We can get a properly configured (for us) production database up in about one half the time using dbassist as it used to take with scripts. And we're not novices. While the databases are not petabyte sized, they do run up to 50G. Van ----------------------------------------------------------- Got questions? Get answers over the phone at Keen.com. Up to 100 minutes free! http://www.keen.com