﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Discuss Content Posted by Jay Dave / Article Discussions / Article Discussions by Author </title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Thu, 24 May 2012 13:27:56 GMT</lastBuildDate><ttl>20</ttl><item><title>A Look at Database Mirroring</title><link>http://www.sqlservercentral.com/Forums/Topic375123-382-1.aspx</link><description>Comments posted here are about the content posted at &lt;A HREF="http://www.sqlservercentral.com/columnists/jDave/3046.asp"&gt;http://www.sqlservercentral.com/columnists/jDave/3046.asp&lt;/A&gt;</description><pubDate>Tue, 19 Jun 2007 16:40:00 GMT</pubDate><dc:creator>sqldba-294117</dc:creator></item><item><title>DB Mirroring Networking Issues</title><link>http://www.sqlservercentral.com/Forums/Topic521636-382-1.aspx</link><description>Hello, I am currently working on a database mirroring setup for 10 databases each under 5 GB.When i enable mirroring on the Principal server, even before i actually start mirroring databases i noticed that network wait increases. I am using Quest Performance Analysis to monitor my Principal and my Mirror. I haven't found documentation on this type of wait (DBmirror Events Queue, DBmirror CMD) and don't know if I should be concerned or if this is normal. As i try to add new databases for mirroring i noticed that these wait events increase and at 5-6 databases network workload starts to be a problem as it rises to 80-90% although performance monitor on both mirror and principal report a maximum of 200 KB / sec transfer.Both Principal and Mirror have a Gbit network card and they're both in the same private lan. If you have any suggestions on what i should monitor please give me a hint.Here is a screenshot of what Q. Perf. Analysis signals as a network performance problem. [URL=http://img45.imageshack.us/my.php?image=pacu6.jpg][IMG]http://img45.imageshack.us/img45/187/pacu6.th.jpg[/IMG][/URL]Thank you.</description><pubDate>Mon, 23 Jun 2008 04:36:18 GMT</pubDate><dc:creator>Zgondea Paul</dc:creator></item><item><title>high safety without automatic failover (sync) resulting slow performance.</title><link>http://www.sqlservercentral.com/Forums/Topic939441-382-1.aspx</link><description>I have done my live database (10gb size) mirroring with high safety [b]without[/b] automatic fail over (synchronous) resulting slow performance. As we have SQL server 2005 [b]std [/b]edition we can not go for asynchronous mode. And we can not go for enterprise edition now due to various other factors. This database is being connected from java web application and my customers are experiencing severe slow performance. Please could someone let me know how to know where and how to start analyzing the issue and possible reasons behind this slow performance like indexes etc...</description><pubDate>Fri, 18 Jun 2010 03:22:14 GMT</pubDate><dc:creator>sivaji</dc:creator></item><item><title>Patching SRDF SQL 2005</title><link>http://www.sqlservercentral.com/Forums/Topic762268-382-1.aspx</link><description>Anyone know best practice for patching sql2005 SRDF pair ?We have Cluster prod server hosting 4 instancesWe have standalone DR hosting 4 instancesData and Log luns are replicated via SRDFA (in system dbs)Binaries installed on C drive local disks for prod and DRHow do we patch DR server1.)Break mirror2.) Install SP3 Patch Production3.) Start SQL services DR (will the start without modification - all startup paths are same as prod)4.) Install SP3 </description><pubDate>Thu, 30 Jul 2009 04:39:02 GMT</pubDate><dc:creator>simon.p.miller</dc:creator></item><item><title>Starting SQL Server in Minimal Configuration</title><link>http://www.sqlservercentral.com/Forums/Topic356913-382-1.aspx</link><description>Comments posted here are about the content posted at &lt;A HREF="http://www.sqlservercentral.com/columnists/jDave/2963.asp"&gt;http://www.sqlservercentral.com/columnists/jDave/2963.asp&lt;/A&gt;</description><pubDate>Mon, 09 Apr 2007 10:40:00 GMT</pubDate><dc:creator>sqldba-294117</dc:creator></item><item><title>Microsoft DPM</title><link>http://www.sqlservercentral.com/Forums/Topic362841-382-1.aspx</link><description>Comments posted here are about the content posted at &lt;A HREF="http://www.sqlservercentral.com/columnists/jDave/2986.asp"&gt;http://www.sqlservercentral.com/columnists/jDave/2986.asp&lt;/A&gt;</description><pubDate>Wed, 02 May 2007 18:54:00 GMT</pubDate><dc:creator>sqldba-294117</dc:creator></item><item><title>SMS Script</title><link>http://www.sqlservercentral.com/Forums/Topic418245-382-1.aspx</link><description>Comments posted to this topic are about the item [B]&lt;A HREF="/scripts/Administration/61433/"&gt;SMS Script&lt;/A&gt;[/B]</description><pubDate>Sat, 03 Nov 2007 09:29:32 GMT</pubDate><dc:creator>sqldba-294117</dc:creator></item><item><title>XML Notepad with SSMS</title><link>http://www.sqlservercentral.com/Forums/Topic377522-382-1.aspx</link><description>Comments posted here are about the content posted at &lt;A HREF="http://www.sqlservercentral.com/columnists/jDave/3060.asp"&gt;http://www.sqlservercentral.com/columnists/jDave/3060.asp&lt;/A&gt;</description><pubDate>Thu, 28 Jun 2007 12:35:00 GMT</pubDate><dc:creator>sqldba-294117</dc:creator></item></channel></rss>
