Chris, Any guides on how to do this in the scenario where I have SQL entirely installed on one drive?
Thanks, Brian Sent from my iPhone > On Mar 12, 2014, at 3:59 PM, "Chris Nackers" <[email protected]> > wrote: > > All other responses have been spot on, the license issue wasn’t a valid > point. > > You should have more drives than C/E anyways for a proper CM install, but it > is what it is. > > In a ideal configuration you would have: > C: OS > D: ConfigMgr Inboxes > E: Data/DP > F: SQL DB > G: SQL TX > > That’s “ideal”, perfect would to be split a few more things up, but for your > size, doubtful you’ll see much of a difference, the main key is to separate > the OS from ConfigMgr from SQL DB from SQL TX. > > Hope that helps. > > Chris Nackers > Microsoft MVP – Enterprise Client Management > Email: [email protected] > Nackers Consulting Services, LLC > > From: [email protected] [mailto:[email protected]] > On Behalf Of Brian McDonald > Sent: Wednesday, March 12, 2014 11:06 AM > To: [email protected] > Subject: RE: [mssms] Moving SCCM 2012 DB > > Thanks for everyone who responded. Here's my next question. In my > environment, my SQL DBA installed SQL on my Primary Site Server. I know, I > know....:( > > I have 2 drives on my Primary Site. C:\ has SCCM Installed and E:\ has SQL > installed. > > How difficult of a task would it be to move the DB directory, logs directory, > tempDB directory, tempDB files, etc. etc. to separate drives? > > Would I be looking at a complete reinstall of SQL? How would this impact my > current SCCM 2012 environment? Is it too risky to do at this point. Trying to > determine my options and best recommendations on how to move forward. > > Thanks! > > Brian > > From: [email protected] > To: [email protected] > Subject: RE: [mssms] Moving SCCM 2012 DB > Date: Wed, 12 Mar 2014 14:47:24 +0000 > > 1. It’s already installed in a Microsoft supported configuration > 2. Moving it will mean generating a fair amount of network traffic > between the two servers whereas it is presently all local > 3. Generally speaking, your data is more secure staying put on one > server than moving it from one server to another > 4. IIRC, they cannot use that SQL license to collocate other > application databases…it’s ONLY for ConfigMgr (need to verify that one > though). So unless they have a separate SQL license for the other server, > they’re either dedicating another whole server just for ConfigMgr or they’re > wasting the license > > IMO, they’re the ones with the burden of proof in this situation. They would > need to demonstrate how moving data across a network between servers is less > secure than having it all local. > > -Phil > _________________________________________________________________ > Phil Schwan | Technical Architect, Enterprise Windows Services > Project Leadership Associates | 2000 Town Center, Suite 1900, Southfield, MI > 48075 > Lync: 312.756.1626 Mobile: 419.262.5133 > www.projectleadership.net > <image001.jpg>Lead with Strategy. Leverage Technology. Deliver Results. > <image002.jpg><image003.jpg> <image004.jpg> > > > > From: [email protected] [mailto:[email protected]] > On Behalf Of Brian McDonald > Sent: Wednesday, March 12, 2014 10:34 AM > To: [email protected] > Subject: [mssms] Moving SCCM 2012 DB > > Hi everyone, > > My DBA has asked me to move my local SQL install remote. I have a single > primary site with 64 GB of memory and service only 1200 clients total. I see > no reason to move the SQL to a remote location. They basically told me there > reasoning was from a security standpoint. First reason was because local > install required a local SQL instance (licensing), which we explained to them > we are using STD edition and licensing is included. > > I need a strong business case to keep my SQL install local. I see no reason > to move it off-box. > > Any suggestions? > > Thanks, > > Brian > > > PRIVILEGED AND CONFIDENTIAL. This email and any files transmitted with it are > privileged and confidential and intended solely for the use of the individual > or entity to whom they are addressed. If you have received this email in > error please notify the sender. If you are not the named addressee you should > not disseminate, distribute or copy this e-mail or any of its attachments. > > > >
<<inline: image001.jpg>>
<<inline: image002.jpg>>
<<inline: image003.jpg>>
<<inline: image004.jpg>>
