Change SQL Server
Hello,We've been running Configuration Manager for a few months now, but the Console has been horribly laggy. After some research, it looks like having the SQL Server and the ConfigMgr server running on the same box causes lots of issues. In this case, we want to move the SQL Server to another box we have. Just installed SQL on it, but now I need to know how to move everything over so that I don't start seeing errors spitting out at me. Can someone tell me the easiest way to do this?THanks,
November 25th, 2009 6:04pm

http://technet.microsoft.com/en-us/library/bb680707.aspx
Free Windows Admin Tool Kit Click here and download it now
November 25th, 2009 6:28pm

Moving SQL to another server is unlikely to solve your console slowness issues. It will however increase your troubleshooting of site server issues due to the increase complexity of you setup.http://www.enhansoft.com/
November 25th, 2009 6:29pm

Can you elaborate more on what causes the slowness? Our entire network is running on GbE, and we have fiber connections going to all of our buildings at (I think) 10Gbps. It's really frustrating to use the console when you have to wait for things to happen.
Free Windows Admin Tool Kit Click here and download it now
November 25th, 2009 6:33pm

IMHO, the console needs a lot of work. There are things that you can do to speed it up but I personally have never found that it does much. Console slowness is one of the biggest complaints about ConfigMgr. Moving SQL will (in general) not solve that for you unless your server is currently over worked, which I doubt it is. http://www.enhansoft.com/
November 25th, 2009 7:30pm

Actually, SQL was using about 3 out of 4GB of RAM before we added more RAM to the box. It's still using 3, and it got a little better, but I've still seen many things saying that it helps... I'll see what it does and post, but now I'm not sure.
Free Windows Admin Tool Kit Click here and download it now
November 25th, 2009 7:33pm

You can limit the amount of RAM SQL will use. Try capping SQL at say 1.5 GB this should leave enough for ConfigMgr and the OS. Using SSMS, select the SQL server, right click and select properties, the the Max setting to limit the amount of RAM SQL takes under the memory tab. http://www.enhansoft.com/
November 25th, 2009 7:43pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics