Re: Database Backups & Restores: an in-depth knowledge required

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: evan b (evan_at_cheapaschips.com.au_removethis)
Date: 01/04/05


Date: Wed, 5 Jan 2005 00:54:07 +1030

Well perhaps it's your specs
btw u can run CPUZ to identify bus speeds etc.
If the machines have same quality of equipment and are configured similarly
then I would suggest your ram and dual CPU vs single CPU

If you run the profiler on them as they are backing perhaps you will see
something like mem utilisation etc.
Another thought is how much are the files fragmented the dbs arent huge but
there may be a degree of fragmentation on the file system which slows things
down.

Also how are you restoring from Server A to Server B?

"Griff" <Howling@The.Moon> wrote in message
news:%23wUo43l8EHA.1564@TK2MSFTNGP09.phx.gbl...
> I have two servers.
>
> Server A:
> Dual 2.8 Xeon Processor
> 4 GB RAM
> SQL Server 2000 Enterprise
>
> Server B
> Single 3.0 Xeon Processor
> 2.5 GB RAM
> SQL Server 2000 Standard
>
> I have an identical database on both. The backup file is 1.22 GB, the
data
> file is 1.44 GB and the log file is 504 KB.
>
> When I restore these databases, the restore on server A takes 2.58
minutes,
> but on server B it takes 6.48 minutes (over twice as long).
>
> Similar discrepancies are found when I backup these databases.
>
> I don't understand why!
>
> Studying task manager shows that the CPU usage is minimal and the amount
of
> memory used is minimal, presumably ruling out the speed of the processors
> and the amount of RAM available. If I had multiple data devices then I
> could see the Enterprise version being quicker because it could create
more
> threads for parallel processing, but I don't so this should rule out the
> Enterprise/Standard differences. Oh and both servers run on multiple
> spindle, fast RAID5+1 disks, and these are identical.
>
> So....what is occurring that actually takes the ~ 3 minutes or ~ 7
minutes?
>
> Many thanks
>
> Griff
>
>
>
>



Relevant Pages

  • Re: Alocated Memory Error (SQLSERVR)
    ... but my understanding is that the MSDE instances are designed to ... and you don't want it grabbing all that RAM. ... running but non ever going about 200mb of memory usage. ... Server 2000 SP4, ...
    (microsoft.public.windows.server.sbs)
  • Re: High memory usage (*HELP*)
    ... you can use Computer Management MMC to view the server logs. ... a server with 4 GB RAM, I doubt you need the second page file on D. So ... The virtual memory on D: drive is set to: 1550/3075 ... throttled ISA and Monitoring. ...
    (microsoft.public.windows.server.sbs)
  • Re: High memory usage (*HELP*)
    ... I rebooted the server, I should have just restarted the service for report ... a server with 4 GB RAM, I doubt you need the second page file on D. ... The virtual memory on D: drive is set to: 1550/3075 ...
    (microsoft.public.windows.server.sbs)
  • Re: Alocated Memory Error (SQLSERVR)
    ... FWIW I am not using sbs 2003 premium, ... non ever going about 200mb of memory usage. ... on what you should throttle the RAM to. ... Server 2000 SP4, ...
    (microsoft.public.windows.server.sbs)
  • Re: Windows 2000 Server StandardEdition /PAE Question
    ... specifically the SQL Server 2000 Standard Edition on that server. ... His point is that applications can only use up to 2 GB or RAM on ... a process running under Windows 2000 or Windows Server 2003 can ... used) with some of the memory being physical memory and some being virtual ...
    (microsoft.public.win2000.general)