Feeds:
Beiträge
Kommentare

Archive for August 2013

Ich habe vor kurzen eine Mail erhalten dass die MCM/MCSM/MCA Zertifizierungen zum 1.10. eingestellt werden, das ganze Programm ist quasi abgeschaltet.

Es ist mir schlicht unbegreiflich, mir fehlen ehrlich gesagt die Worte wie man sich dazu entschließen kann? Das Programm an sich ist nicht günstig, weder für die Teilnehmer noch für Microsoft selber, keine Frage. Aber jeder der daran teilgenommen hat weiß wie wertvoll das Programm, die drei Wochen Training in Redmond, der Zugang zur Community etc. etc. ist..

Feedback feedback feedback. Das ist wohl das Gebot der Stunde! Also nur für den Fall dass jemand es auch nicht versteht, vielleicht bin ich mit meiner Meinung ja auch alleine?

 

https://connect.microsoft.com/SQLServer/feedback/details/799431/please-dont-get-rid-of-the-mcm-and-mca-programs

und ein paar weiterführende Links, ich glaube die Liste ließe sich beliebig fortführen:

http://blogs.technet.com/b/neiljohn/archive/2013/08/31/retiring-the-microsoft-master-certifications-and-training.aspx

http://up2v.nl/2013/08/31/microsoft-retires-its-top-level-certifications-mcm-mca-and-mcsm/

 

UPDATE:

Tim Sneath hat auf dieser Connect Seite versucht zu erläutern wie es zu dieser Entscheidung kam und was der Hintergrund ist:

 

Von Tim Sneath am 31.08.2013 um 13:32 bereitgestellt

Thank you for the passion and feedback. We’re reading your comments and take them seriously, and as the person ultimately responsible for the decision to retire the Masters program in its current form, I wanted to provide a little additional context.
Firstly, you should know that while I’ve been accused of many things in my career, I’m not a "bean counter". I come from the community myself; I co-authored a book on SQL Server development, I have been certified myself for nearly twenty years, I’ve architected and implemented several large Microsoft technology deployments, my major was in computer science. I’m a developer first, a manager second.
Deciding to retire exams for the Masters program was a painful decision – one we did not make lightly or without many months of deliberation. You are the vanguard of the community. You have the most advanced skills and have demonstrated it through a grueling and intensive program. The certification is a clear marker of experience, knowledge and practical skills. In short, having the Masters credential is a huge accomplishment and nobody can take that away from the community. And of course, we’re not removing the credential itself, even though it’s true that we’re closing the program to new entrants at this time.
The truth is, for as successful as the program is for those who are in it, it reaches only a tiny proportion of the overall community. Only a few hundred people have attained the certification in the last few years, far fewer than we would have hoped. We wanted to create a certification that many would aspire to and that would be the ultimate peak of the Microsoft Certified program, but with only ~0.08% of all MCSE-certified individuals being in the program across all programs, it just hasn’t gained the traction we hoped for.
Sure, it loses us money (and not a small amount), but that’s not the point. We simply think we could do much more for the broader community at this level – that we could create something for many more to aspire to. We want it to be an elite community, certainly. But some of the non-technical barriers to entry run the risk of making it elitist for non-technical reasons. Having a program that costs candidates nearly $20,000 creates a non-technical barrier to entry. Having a program that is English-only and only offered in the USA creates a non-technical barrier to entry. Across all products, the Masters program certifies just a couple of hundred people each year, and yet the costs of running this program make it impossible to scale out any further. And many of the certifications currently offered are outdated – for example, SQL Server 2008 – yet we just can’t afford to fully update them.
That’s why we’re taking a pause from offering this program, and looking to see if there’s a better way to create a pinnacle, WITHOUT losing the technical rigor. We have some plans already, but it’s a little too early to share them at this stage. Over the next couple of months, we’d like to talk to many of you to help us evaluate our certifications and build something that will endure and be sustainable for many years to come.
We hate having to do this – causing upset amongst our most treasured community is far from ideal. But sometimes in order to build, you have to create space for new foundations. I personally have the highest respect for this community. I joined the learning team because I wanted to grow the impact and credibility of our certification programs. I know this decision hurts. Perhaps you think it is wrong-headed, but I wanted to at least explain some of the rationale. It comes from the desire to further invest in the IT Pro community, rather than the converse. It comes from the desire to align our programs with market demand, and to scale them in such a way that the market demand itself grows. It comes from the desire to be able to offer more benefits, not fewer. And over time I hope we’ll be able to demonstrate the positive sides of the changes we are going through as we plan a bright future for our certifications.
Thank you for listening… we appreciate you more than you know.
Tim Sneath

Advertisements

Read Full Post »

Hallo zusammen,

 

es soll ja Gerüchte gegeben haben dass an der Unterstützung des SQL Clusters in Lync 2013 gearbeitet wurde. Das ist so nicht mehr richtig. Also dass es sich hierbei um ein Gerücht handelt. Kürzlich wurden die relevanten Technet Artikel aktualisiert – SQL Cluster ist nun offiziell und vollständig supported!

 

http://technet.microsoft.com/en-us/library/gg398990.aspx

 

Lync Server 2013 supports the user of either SQL mirroring or SQL clustering for each Lync Server database. You can easily set up SQL mirroring with the Topology Builder tool in Lync Server 2013. For SQL failover clustering, you must use SQL Server for setup.

Lync Server 2013 supports SQL clustering topologies for all deployments, including greenfield deployments and organizations that have upgraded from previous versions of Lync Server.

SQL Clustering support is for an active/passive configuration. For performance reasons, the passive node should not be shared by any other SQL instance.

The following support is included:

  • Two-node failover clustering for the following:
    • Microsoft SQL Server 2012 Standard (64-bit edition). Additionally running the latest service pack is recommended.
    • Microsoft SQL Server 2008 R2 Standard (64-bit edition). Additionally running the latest service pack is recommended.
  • Up to sixteen-node failover clustering for the following:
    • Microsoft SQL Server 2012 Enterprise (64-bit edition). Additionally running the latest service pack is recommended.
    • Microsoft SQL Server 2008 R2 Enterprise database software (64-bit edition). Additionally running the latest service pack is recommended.

For more information about SQL mirroring, see Back End Server High Availability. For details on how to deploy SQL clustering, see Configure SQL Server Clustering.

Dies betrifft ausdrücklich den ‘klassischen SQL Cluster’ – das Feature AlwaysOn ist nach wie vor nicht getestet = nicht supported. Lync Server 2013 hat ja auch eine relativ enge Integration in die Mirror-Konfiguration des SQL Servers, angefangen von der automatischen Konfiguration des Mirror bis hin zur Möglichkeit das Failover aus der Lync Shell heraus zu initiieren. Dies ist m.w. beim Cluster nicht so gegeben, wobei man sich nun vortrefflich darüber streiten kann obs das braucht und ob Mirror oder Cluster oder nicht doch noch eine weitere HA-Strategie die ‘richtige’ sei.

Aber wir haben nun Optionen was SQL angeht, und das ist es doch worauf es ankommt Smiley

 

UPDATE:

Es wurde nun schon einige Male nachgefragt, darum möchte ich auch auf diese Frage eingehen: Kann ich auf einem leistungsfähigen SQL Cluster mehrere Backend-Datenbanken unterschiedlicher FrontEnd Pools gemeinsam betreiben? Gibt es ein Colocaltion-Szenario hierfür?

Auf dieser Frage gibt es eine sehr eindeutige Antwort im Technet:

http://technet.microsoft.com/en-us/library/gg398102.aspx

    • Each instance of SQL Server can contain only a single back-end database, a single Monitoring database, a single Archiving database, a single Persistent Chat database, and a single Persistent Chat compliance database.
    • The database server cannot support more than one Front End pool, one Archiving deployment, and one Monitoring deployment, but it can support one of each, regardless of whether the databases use the same instance of SQL Server or separate instances of SQL Server.

Nein, jeder SQL-Server / Cluster darf jeden Datenbanktyp nur einmal hosten, unabhängig von der Anzahl der Instanzen. Dies ist so auch schon durch den Topology Editor implementiert, dieser lässt es nicht zu auf den gleichen FQDN mehr als eine Backend-Datenbank zu legen.

Read Full Post »