Ed Miller
My LACK of SQL knowledge fills volumes.!!
>
> > Ed Miller wrote:
> > >
> > > > Its designed to not be demanding on the system. There are some
things
> > > > you can look at to speed it up, but mostly is giving your SQL Server
> > > > more RAM (and configuring SQL Server to use it).
> > >
> > > In configuration I have the tempdb ram set at 96MB on a 128 MB system
> > > What else should I look at?
> >
> > Ouch! Thats pretty bad. What do you have your memory set at? For a
> > 128mb
> > physical ram system with nothing else running on the SQL Server, I would
> > set tempdb in ram to 24mb, and the memory to 32768 (64mb of ram). You
> > might also try set tempdb in RAM to 0 (so that its on disk) and setting
> > the memory to 44000 (88mb).
> >
> I changed to the 0 tempdb setting and now it will not start.
> Below is the error log when I try to start.:
> I have Radius running on a real old db. But I am running out of time.
>
>
> HELP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> I need to talk to someone.
>
> 99/06/28 09:15:17.88 kernel Microsoft SQL Server 6.50 - 6.50.281 (Intel
> X86)
> Nov 4 1997 17:58:00
> Copyright (c) 1988-1997 Microsoft Corporation
>
> 99/06/28 09:15:17.88 kernel Copyright (C) 1988-1994 Microsoft
Corporation.
> 99/06/28 09:15:17.88 kernel All rights reserved.
> 99/06/28 09:15:17.88 kernel Logging SQL Server messages in file
> 'C:\MSSQL\LOG\ERRORLOG'
> 99/06/28 09:15:17.89 kernel initconfig: number of user connections
limited
> to 30
> 99/06/28 09:15:17.89 kernel SQL Server is starting at priority class
> 'normal' with dataserver semaphore = 1 (1 CPU detected, SMPStat=1).
> 99/06/28 09:15:17.90 server LogLRU buffers: 0
> 99/06/28 09:15:17.92 kernel Attempting to initialize Distributed
> Transaction Coordinator
> 99/06/28 09:15:19.98 kernel initializing virtual device 0,
> C:\MSSQL\DATA\MASTER.DAT
> 99/06/28 09:15:19.98 kernel Opening Master Database ...
> 99/06/28 09:15:19.99 spid1 Loading SQL Server's default sort order and
> character set
> 99/06/28 09:15:19.99 spid1 Recovering Database 'master'
> 99/06/28 09:15:19.99 spid1 Recovery dbid 1 ckpt (8454,24) oldest
> tran=(8454,0)
> 99/06/28 09:15:20.02 spid1 Activating disk 'Domain'
> 99/06/28 09:15:20.03 kernel initializing virtual device 6,
> C:\MSSQL\DATA\Domain.DAT
> 99/06/28 09:15:20.03 spid1 Activating disk 'Emerald'
> 99/06/28 09:15:20.03 kernel initializing virtual device 4,
D:\Emerald.DAT
> 99/06/28 09:15:20.03 kernel mirror: c:\emerald.mir
> 99/06/28 09:15:20.03 spid1 Activating disk 'MQISData'
> 99/06/28 09:15:20.03 kernel initializing virtual device 2, C:\Program
> Files\MSMQ\MQISData.dat
> 99/06/28 09:15:20.03 spid1 Activating disk 'MQISLog'
> 99/06/28 09:15:20.03 kernel initializing virtual device 3, C:\Program
> Files\MSMQ\MQISLog.dat
> 99/06/28 09:15:20.03 spid1 Activating disk 'MSDBData'
> 99/06/28 09:15:20.04 kernel initializing virtual device 127,
> C:\MSSQL\DATA\MSDB.DAT
> 99/06/28 09:15:20.04 spid1 Activating disk 'MSDBLog'
> 99/06/28 09:15:20.04 kernel initializing virtual device 126,
> C:\MSSQL\DATA\MSDBLOG.DAT
> 99/06/28 09:15:20.04 spid1 server name is 'TESTIE'
> 99/06/28 09:15:20.04 spid1 Recovering database 'model'
> 99/06/28 09:15:20.04 spid1 Recovery dbid 3 ckpt (337,13) oldest
> tran=(337,0)
> 99/06/28 09:15:20.07 spid1 Clearing temp db
> 99/06/28 09:15:20.07 spid1 CREATE DATABASE failed. Could not allocate
> enough disk space for a new database on the disks named in the command.
> Total space allocated must be at least 1 Mbytes (511 2048-byte pages) to
> accommodate copy of Model Database.
> 99/06/28 09:15:20.07 spid1 Problem creating Temporary Database - if out
> of space, please extend and reboot. If some other problem, please contact
> Technical Support.
> 99/06/28 09:15:20.07 kernel Failed to create temp db
>
>