RE: SQL Server 2005 64 bit on Window Server 2003 R2 64bit slow per

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Jason,

You may think this is a dumb question - but it has to be asked. Is the
64bit versions of OS and SQL Server installed (not 32bit by mistake)? It's
easy to get wrong.

Tim GJ

"Jason Wilson" wrote:

Thanks for the reply. I have seen 3 of these unrelated boxes with this OS
and version of SQL perform terribly on different hardware configs. Something
is just not right, and these kinds of problems usually aren't too hard to
find when the problems are this prevalent. There has to be some basic setup
things for 64 bit that folks are missing.

Jason

"Linchi Shea" wrote:

If you are suspecting performance problem with the box, I'd suggest
benhcmarking each aspect--CPU, memory, disk, and network, and compare the
results to some other box that you have used for a while and are comfortable
with. For instance, you can use the stream benchmark to measure the memory
speed on the box, and check if there is any issue with reading from memory to
the registers or writing to memory from the registers.

If the box itself checked out fine, then move on to runnign SQL Server on
the box.

Linchi

"Jason Wilson" wrote:

I have done all the SQL Server debugging I know to do. Memory usage,
Perfmon, Disk I/O, Pages, Profiler traces, checked locks/blocks, long running
queries by CPU and Disk I/O, updated DB stats/indexes, tuned TempDB,
truncated transaction logs. checked network protocols, checked the HOSTS
file, I have even tried clearing the cache. I don't know what the hold up
is, but these boxes are absolute dogs! Even Reporting Services seems to run
slow on these boxes to me.

Jason

"Linchi Shea" wrote:

I don't believe you can attribute the performance issue to the difference
between 32-bit and 64 bit. To troubleshoot, I'd first take SQL Server out of
the picture, and run some generic benchmarks to check the box out.

With SQL Server, I'd troubleshoot the performance the same way as usual,
i.e. to identify the performance bottleneck first: is the performance bad
because of processors, memoty, disks, etc? That may lead to the discovery of
a corresponding configuration issue.

Linchi

"Jason Wilson" wrote:

We have a new 8 proc 64 bit SQL Server with 16 GB of RAM (Windows 2003 Server
R2 Enterprise Ed.), and we are running VERY small test and the performance is
terrible. This is the second one of these servers I have seen this happen
on. The boxes perform worse than our developers 32 bit XP boxes with a
single disk drive and they run more aps than we are running on these servers.
These servers are completely different boxes from different vendors in
different places on different networks.

There is something we are missing in the setup/config apparently. Any
suggestion/ideas would be very welcomed!!! We have setup quite a few 32 bit
systems with no problems. Right now it looks like we have wasted a lot of
money on hardware and software!!! Please help!
.

Relevant Pages

  • RE: SQL Server 2005 64 bit on Window Server 2003 R2 64bit slow per
    ... even gone as far as swapping network cables and updating NIC card drivers to ... If the box itself checked out fine, then move on to runnign SQL Server on ... Perfmon, Disk I/O, Pages, Profiler traces, checked locks/blocks, long running ... slow on these boxes to me. ...
    (microsoft.public.sqlserver.setup)
  • RE: SQL Server 2005 64 bit on Window Server 2003 R2 64bit slow per
    ... you can use the stream benchmark to measure the memory ... If the box itself checked out fine, then move on to runnign SQL Server on ... Perfmon, Disk I/O, Pages, Profiler traces, checked locks/blocks, long running ... slow on these boxes to me. ...
    (microsoft.public.sqlserver.setup)
  • RE: SQL Server 2005 64 bit on Window Server 2003 R2 64bit slow per
    ... I have seen 3 of these unrelated boxes with this OS ... If the box itself checked out fine, then move on to runnign SQL Server on ... Perfmon, Disk I/O, Pages, Profiler traces, checked locks/blocks, long running ...
    (microsoft.public.sqlserver.setup)
  • Re: Determine Disk Block Size ?
    ... As always, thanks Andrew. ... Most of the documentation for 2000 is wrong in that it may state you need multiple files to spawn multiple threads. ... >> The MS SQL Server Operations Manual makes a recommendation of using 64-KB>> cluster sizes. ... We have done so with a dramatic total disk I/O>> throughput. ...
    (microsoft.public.sqlserver.server)
  • Re: Nearest Common Ancestor Report (XDb1s $1000 Challenge)
    ... Hugo. ... > tempdb (used by SQL Server to store intermediate result sets) is on the ... My Windows page file is on that hard disk as well (though ... elapsed time was disk I/O latency vs. CPU time. ...
    (comp.object)