<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://richmondsql.org/cs2007/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Search results matching tags 'mirror' and 'cluster'</title><link>http://richmondsql.org/cs2007/search/SearchResults.aspx?o=DateDescending&amp;tag=mirror,cluster&amp;orTags=0</link><description>Search results matching tags 'mirror' and 'cluster'</description><dc:language>en-US</dc:language><generator>CommunityServer 2007.1 (Build: 20917.1142)</generator><item><title>Re: Comparing SQL Mirroring to Clustering</title><link>http://richmondsql.org/cs2007/forums/p/18/20.aspx#20</link><pubDate>Fri, 21 Mar 2008 14:52:06 GMT</pubDate><guid isPermaLink="false">2e8a3759-4cfd-4c9f-8103-2483fc393c1e:20</guid><dc:creator>fibrock</dc:creator><description>&lt;span style="FONT-SIZE:10pt;COLOR:black;FONT-FAMILY:&amp;#39;Arial&amp;#39;,&amp;#39;sans-serif&amp;#39;;"&gt;I like the idea of a round table on this topic, because not many of us have a lot of experience with clustering and or mirroring.&amp;nbsp; Currently we use both Clustering and Mirroring for our production environments.&amp;nbsp; Clustering has given us more of a headache than Mirroring due to some SAN management issues with presentation of disk to the cluster and the ID&amp;#39;s that the OS is assigning these disks.&amp;nbsp; We have worked these issues out with our SAN team and they are no longer an issue but we switched to Mirroring for a few of applications because of this.&amp;nbsp; We have not had any significant issues with mirroring, which is running on an OLTP database that controls a pricing system.&amp;nbsp; While this is an OLTP system it does have a low level of transactions.&amp;nbsp; We run without a witness and therefore without automatic fail over, in the high performance asynchronous mode.&amp;nbsp; The reason for this is so we do not get any false system failovers, and our applications cannot take advantage of the newer SQL Server OLEDB drivers to allow for automatic failover.&lt;/span&gt;&lt;span style="FONT-SIZE:10pt;COLOR:black;FONT-FAMILY:&amp;#39;Arial&amp;#39;,&amp;#39;sans-serif&amp;#39;;"&gt;I like the idea of a few round table meetings a year in general.&lt;/span&gt; 
&lt;p&gt;&amp;nbsp;&lt;/p&gt;</description></item><item><title>Comparing SQL Mirroring to Clustering</title><link>http://richmondsql.org/cs2007/forums/p/18/19.aspx#19</link><pubDate>Fri, 21 Mar 2008 13:33:51 GMT</pubDate><guid isPermaLink="false">2e8a3759-4cfd-4c9f-8103-2483fc393c1e:19</guid><dc:creator>wkhazzard</dc:creator><description>&lt;p&gt;&lt;font face="courier new,courier"&gt;I&amp;#39;d like to hear the thoughts of other DBAs and Architects who&amp;#39;ve used both SQL Mirroring and SQL Clustering. My company, SnagAJob.com, is currently using SQL Mirroring for our production OLTP databases. We have issues almost every day: mysterious failovers, ADO.NET clients that repeatedly attempt to connect to the mirrored server instead of the primary (because they believe it&amp;#39;s failed over). We&amp;#39;re fairly certain that it&amp;#39;s not networking issues because we see these same issues in our lab environment when everything is connected on a single gigabit switch. This would be a great topic for a future meeting, in my opinion, especially as more of a round-table type of discussion.&lt;/font&gt;&lt;/p&gt;</description></item></channel></rss>