<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: OCS 2007 R2 Monitoring Role FAQ</title>
	<atom:link href="http://blog.insideocs.com/2010/01/28/ocs-2007-r2-monitoring-role-faq/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.insideocs.com/2010/01/28/ocs-2007-r2-monitoring-role-faq/</link>
	<description>Microsoft Office Communications Server - Tips, Tricks, and Insight</description>
	<lastBuildDate>Thu, 26 Jan 2012 18:22:01 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Curtis Johnstone</title>
		<link>http://blog.insideocs.com/2010/01/28/ocs-2007-r2-monitoring-role-faq/comment-page-1/#comment-8126</link>
		<dc:creator>Curtis Johnstone</dc:creator>
		<pubDate>Wed, 27 Jul 2011 21:03:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.insideocs.com/?p=756#comment-8126</guid>
		<description>Hi,

Yes you can re-use the Standard Edition back-end database server to house the Monitoring database (I&#039;ve seen it in several production sites).

There are a couple of caveats (i.e. performance).  More details are available in the blog post you are commenting on (	http://blog.insideocs.com/2010/01/28/ocs-2007-r2-monitoring-role-faq/
).

When you install the QoE monitoring server (role), just point the monitoring database to the backend SQL server during the install. By default it will install into a seperate database - as long as you do not manually alter the default names to conflict with the back-end database!  The backend databases are named &quot;rtc&quot;, &quot;rtcab&quot;, &quot;rtcconfig&quot;, &quot;rtcdyn&quot;, etc...

Curtis</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Yes you can re-use the Standard Edition back-end database server to house the Monitoring database (I&#8217;ve seen it in several production sites).</p>
<p>There are a couple of caveats (i.e. performance).  More details are available in the blog post you are commenting on (	<a href="http://blog.insideocs.com/2010/01/28/ocs-2007-r2-monitoring-role-faq/" rel="nofollow">http://blog.insideocs.com/2010/01/28/ocs-2007-r2-monitoring-role-faq/</a><br />
).</p>
<p>When you install the QoE monitoring server (role), just point the monitoring database to the backend SQL server during the install. By default it will install into a seperate database &#8211; as long as you do not manually alter the default names to conflict with the back-end database!  The backend databases are named &#8220;rtc&#8221;, &#8220;rtcab&#8221;, &#8220;rtcconfig&#8221;, &#8220;rtcdyn&#8221;, etc&#8230;</p>
<p>Curtis</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Riya</title>
		<link>http://blog.insideocs.com/2010/01/28/ocs-2007-r2-monitoring-role-faq/comment-page-1/#comment-8118</link>
		<dc:creator>Riya</dc:creator>
		<pubDate>Wed, 27 Jul 2011 12:02:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.insideocs.com/?p=756#comment-8118</guid>
		<description>Hi , 
I am deploying a QoE monitoring server for an standard edition OCS deployment . I want to reuse the back-end database for Monitoring database. Since that automatically gets installed while installing FE , could you please tell me if I can reuse the same and how should I go about that ? 

Regards</description>
		<content:encoded><![CDATA[<p>Hi ,<br />
I am deploying a QoE monitoring server for an standard edition OCS deployment . I want to reuse the back-end database for Monitoring database. Since that automatically gets installed while installing FE , could you please tell me if I can reuse the same and how should I go about that ? </p>
<p>Regards</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Managing OCS 2007 R2 QoE and CDR Data &#171; Inside OCS</title>
		<link>http://blog.insideocs.com/2010/01/28/ocs-2007-r2-monitoring-role-faq/comment-page-1/#comment-2922</link>
		<dc:creator>Managing OCS 2007 R2 QoE and CDR Data &#171; Inside OCS</dc:creator>
		<pubDate>Thu, 08 Jul 2010 23:48:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.insideocs.com/?p=756#comment-2922</guid>
		<description>[...] high-level information about the OCS 2007 R2 Monitoring role: OCS 2007 R2 Monitoring Role FAQ (InsideOCS [...]</description>
		<content:encoded><![CDATA[<p>[...] high-level information about the OCS 2007 R2 Monitoring role: OCS 2007 R2 Monitoring Role FAQ (InsideOCS [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OCS Quality of Experience (QoE) - Quick Facts &#171; Inside OCS</title>
		<link>http://blog.insideocs.com/2010/01/28/ocs-2007-r2-monitoring-role-faq/comment-page-1/#comment-1656</link>
		<dc:creator>OCS Quality of Experience (QoE) - Quick Facts &#171; Inside OCS</dc:creator>
		<pubDate>Fri, 29 Jan 2010 02:26:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.insideocs.com/?p=756#comment-1656</guid>
		<description>[...] Note: If you are deploying the OCS 2007 R2 Monitoring Role, there is an updated (Jan 2010) post with answers to key questions about deployment: see OCS 2007 R2 Monitoring Role FAQ. [...]</description>
		<content:encoded><![CDATA[<p>[...] Note: If you are deploying the OCS 2007 R2 Monitoring Role, there is an updated (Jan 2010) post with answers to key questions about deployment: see OCS 2007 R2 Monitoring Role FAQ. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

