Moving everything wouldn't be that hard. Just need to configure inside SQL management studio.
He's a real DBA? Because installing SQL entirely on the same drive ils against everything he learned in the past. Le 12 mars 2014 17:06, "Brian McDonald" <[email protected]> a écrit : > 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 > > *[image: Description: Description: Description: Arrow email]**Lead with > Strategy. Leverage Technology. Deliver Results.* > > [image: linkedin_logo-19x20] <http://www.linkedin.com/in/philschwan>[image: > Twitter-Logo1-20x20] <https://twitter.com/philschwan> [image: > wordpress-logo3] <http://myitforum.com/myitforumwp/author/philschwan> > > > > > > > > *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: image002.jpg>>
<<inline: image001.jpg>>
<<inline: image004.jpg>>
<<inline: image003.jpg>>
