downloadkid

I remember asking a very similar question not so long ago........here's my understanding. People are right for a SQL VM you need 4 cores and a good 8Gb of RAM - SQL is a pig, it will eat up as much memory as you allow it - it's apparently designed to do just that for faster responses. Now if you're SQl kiddie you could probably tweak it to perform just right for it's maximum load........BUT that is not the most important thing when it comes to a VM SQL. Remember with a SAN you can create various LUNs - LUN0 might be a 2 disk RAID 1 for the various server OSes, LUN1 could be RAID 5 for those servers additional drives - but no matter how you set it up, it's about IOPS. For instance if you have a SQL that is heavily used, on a VM that is sat on a RAID 1 2 disk LUN you probably find that it will suffer lengthy disk queues - this is not a limitation of the RAID level as such but a limitation of the physical drive itself , it's own buffers. The tendancy now days is to go for BIG drives on a SAN - 2 1 TB drives in RAID 1 for a SQL would give you loads of room - but only 2 buffers, one in each drive. The smart money would be to have several drives in maybe a RAID 10 that would share the requests seriously reducing the IOPS increasing perfomance. In short the more spindles the better. This or course is the great thing about VM - if it turns out it's not performing as you would like, create another LUN with more spindles and move it!!

Just came accross your post - thought I 'd ask - did you check the switch logs for broken packets, runts etc. quite often things like this can be caused by a port mis-match; auto on one end, 100 full the other. Then what happens is that as broken packets are dumped by the recieving node which then proceeds to send out a resend request. So traffic builds up quick, worse case senario a broadcast storm.

or just a create a favourite in the browser via group policy

I remember something similar to this with some Dell machines a while back - i dont remember the detail but it was to do with the fact the DHCP requests were being sanctioned before the NIC was initialised - or course it was a driver issue but you could change the sttings on the card - basically it times out. I'm sorry I can't be of anymore help - getting old memory failing!!!!!!

PokerMunkee need a bit more detail; do all users on all vlans require access to the 3870? Conversely do users on the 3870 vlans require access to the core, I assume the core is where the servers are housed, authentication etc? Do you have a tolopolgy drawing you can up?

Evening everyone; has anyone managed to get this working over the LAN off a Server 2008 R2 box - I've installed it as per the instructiuons, nothing too taxing. However when you launch the program it stays stuck at the loading screen with a rotating hour glass. I've contacted the publishers support dept but have had no response as yet. Any advice would be appreciated............... Wophila!