Hi:
I don’t think it’s a technical thing with us more as it’s a
standards thing, our DBA team want to minimize the number of random SQL servers
around the company. I can’t entirely blame them since we ran across a rogue
SQL 2000 box running out of one of our remote offices a while ago that people
had kind of forgotten about, well accept those people using it, long story. So
I see in principle the reasons for wanting to put all databases on centrally
maintainable clusters, and quite frankly in the long term as the SCCM admin I
really don’t care where the database is, especially for a setup this small.
For an SCCM site with under 100 clients, mainly used for managing Windows
updates, controlled restarts and software inventory, I don’t think performance
is a valid argument either way, that server will be doing nothing most of the
time anyway. So I’m taking the attitude that on box will really be better, but
if they want it off box I’m not going to argue for this.
OK, so I got asked on my way in this morning, always on is out
of the picture, is a mirrored secondary supported? Just starting to do
research into this now to see.
Thanks again.
Ryan
From: [email protected] [mailto:[email protected]] On
Behalf Of Jason Wallace
Sent: Thursday, December 26, 2013 11:41 PM
To: [email protected]
Subject: Re: [mssms] RE: using SCCM 2012R2 with SQL 2012 Always On?
Ryan
I would have to agree with you. I see no justification whatsoever for a remote
SQL server although I often do get DBAs wanting it remote.
If you do maintain everything local then it is quite feasible to run something
like Hyper-V replica on the entire VM and take snapshots on, say a 15 minute
schedule. That gives you good, fast recoverability in the event of a failure.
In your instance then since it is you who as the application owner will need to
write the DR documentation then you should be able to state what you need.
On 27 Dec 2013, at 00:06, "Ryan Shugart"
<[email protected]<mailto:[email protected]>> wrote:
Thanks for the replies everyone. Yes, our SQL server is remote. I was really
pushing for the SQL server to be on box, this is a site that will have under
100 clients in it so see no reason why a remote SQL is necessary but got
overruled by the DB guys. I’m going to reach out to Microsoft tomorrow and see
what they have to say about this and if I can get any clearer answers.
However, I will not run an unsupported configuration, even if it “should work.”
Especially for something like this, in my understanding of what an SQL always
on config is, I’m not sure it brings any benefit to SCCM in the configuration
we’ll be using it.
Thanks again.
Ryan
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of
[email protected]<mailto:[email protected]>
Sent: Thursday, December 26, 2013 3:27 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: using SCCM 2012R2 with SQL 2012 Always On?
They probably didn’t test it enough to feel comfortable supporting it.
You can always reach out through your TAM (Technical Account Manager) for a
answer from the product team.
Or if your lucky, one of the MS guys will reply to this next week. ;)
Christopher Catlett
Consultant | Detroit
<image001.jpg>
Sogeti USA
Office 248-876-9738 |Fax 877.406.9647
26957 Northwestern Highway, Suite 130, Southfield, MI 48033-8456
www.us.sogeti.com<http://www.us.sogeti.com/>
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Ryan Shugart
Sent: Thursday, December 26, 2013 5:13 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: using SCCM 2012R2 with SQL 2012 Always On?
OK, follow up to this, does anyone know why always on isn’t supported for SCCM?
I’m asking because I’m getting a lot of push back from our DBA and application
team to do an install in an always on configuration, I personally don’t care
either way, so am not sure why MS just doesn’t go ahead and support this. Is
there something in how SCCM talks to SQL where this won’t work?
Thanks.
Ryan
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of
[email protected]<mailto:[email protected]>
Sent: Thursday, December 26, 2013 12:35 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: using SCCM 2012R2 with SQL 2012 Always On?
http://blogs.technet.com/b/schadinio/archive/2013/05/19/sql-server-2012-alwayson-support-for-system-center-2012-sp1-products.aspx
Unsupported on 2012 sp1, and I haven’t seen any documentation stating otherwise
for R2.
Christopher Catlett
Consultant | Detroit
<image001.jpg>
Sogeti USA
Office 248-876-9738 |Fax 877.406.9647
26957 Northwestern Highway, Suite 130, Southfield, MI 48033-8456
www.us.sogeti.com<http://www.us.sogeti.com/>
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Jason Sandys
Sent: Thursday, December 26, 2013 1:23 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: using SCCM 2012R2 with SQL 2012 Always On?
It’s unsupported to my knowledge.
J
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Ryan Shugart
Sent: Thursday, December 26, 2013 12:04 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] using SCCM 2012R2 with SQL 2012 Always On?
Hi:
Has anyone installed the SCCM 2012R2 database into an SQL 2012 Always
On configuration? I’ve done some poking around and have not found anything
indicating this would be any different from a normal SQL setup for SCCM but
wanted to check.
Thanks.
Ryan
Ryan Shugart
LAN Administrator
MiTek USA, MiTek Denver
314-851-7414
© COPYRIGHT, MITEK HOLDINGS, INC., 2011-2013, ALL RIGHTS RESERVED
________________________________
This communication (including any attachments) contains information which is
confidential and may also be privileged. It is for the exclusive use of the
intended recipient(s). If you are not the intended recipient(s), please note
that any distribution, copying, or use of this communication or the information
in it is strictly prohibited. If you have received this communication in error,
please notify the sender immediately and then destroy any copies of it.
© COPYRIGHT, MITEK HOLDINGS, INC., 2011-2013, ALL RIGHTS RESERVED
________________________________
This communication (including any attachments) contains information which is
confidential and may also be privileged. It is for the exclusive use of the
intended recipient(s). If you are not the intended recipient(s), please note
that any distribution, copying, or use of this communication or the information
in it is strictly prohibited. If you have received this communication in error,
please notify the sender immediately and then destroy any copies of it.
© COPYRIGHT, MITEK HOLDINGS, INC., 2011-2013, ALL RIGHTS RESERVED
________________________________
This communication (including any attachments) contains information which is
confidential and may also be privileged. It is for the exclusive use of the
intended recipient(s). If you are not the intended recipient(s), please note
that any distribution, copying, or use of this communication or the information
in it is strictly prohibited. If you have received this communication in error,
please notify the sender immediately and then destroy any copies of it.
© COPYRIGHT, MITEK HOLDINGS, INC., 2011-2013, ALL RIGHTS RESERVED
________________________________
This communication (including any attachments) contains information which is
confidential and may also be privileged. It is for the exclusive use of the
intended recipient(s). If you are not the intended recipient(s), please note
that any distribution, copying, or use of this communication or the information
in it is strictly prohibited. If you have received this communication in error,
please notify the sender immediately and then destroy any copies of it.
