December 20, 2010 at 12:41 am
CPU's are only running at 65-80 %, it's dual CPU dual core machine, part of it is due to calculations taking place in the ETL process. The only waits I can obeserve is different latch waits and I believe that is ok.
ETL is run as an SSIS package.
/Staffan
December 20, 2010 at 12:42 am
Memory is all 28 Gb( 4 Gb left for OS) allocated to SQL server.
/S
December 29, 2010 at 7:06 am
SS 2005, Win 2003 Server, running under ESXi 4.0, 3ware controller, Crucial SSDs.
We started out with one 3ware 9650 controller that apparently could not keep up and so it corrupted our databases. We worked with 3ware support and we are now also running a 9750-4i to run these SSDs in RAID, leaving the 9650 for the spindles. I have yet to move any files back on to the array for testing. Make backups AND pay attention to what is going on in the environment. You best be running DBCC's and staying on top of it. Work with the vendors and manufacturers as much as possible - even if you spec everything out with plenty of fudge, you just never know.
My opinion would be that the most prominent performance boost would be from tempdb and log files being on the SSD. Since changes are written back to the db file lazilly does it make sense that it is not as critical to have them on SSD? But I guess it all depends on whether your heavy transactional or heavy reads.
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply