<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: SQL SERVER &#8211; 10 Reasons for Database Outsourcing</title>
	<atom:link href="http://blog.sqlauthority.com/2009/05/10/sql-server-10-reasons-for-database-outsourcing/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sqlauthority.com/2009/05/10/sql-server-10-reasons-for-database-outsourcing/</link>
	<description>Personal Notes of Pinal Dave</description>
	<lastBuildDate>Thu, 09 Feb 2012 10:40:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Sean</title>
		<link>http://blog.sqlauthority.com/2009/05/10/sql-server-10-reasons-for-database-outsourcing/#comment-51927</link>
		<dc:creator><![CDATA[Sean]]></dc:creator>
		<pubDate>Fri, 15 May 2009 14:43:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=4885#comment-51927</guid>
		<description><![CDATA[It&#039;s not just the bandwidth you have to consider, it&#039;s also the latency. And then, you still have to consider the office&#039;s bandwidth. If you are outsourcing your internal system databases (CRM, for example) - then instead of having a gigE connection, you might only have a 30mbps fiber connection. Or maybe only a T1, depending on the size of the company.

Latency though is the major killer. If the company hosting your databases has a fat pipe, and you have a fat pipe, but the hops in between have issues, then you are setting yourself up for mad employees.

IMO, database outsourcing should only be considered as a last resort if your company can&#039;t justify the expense of hardware and staff to maintain their own datacenter/servers and database software.

It is probably more cost effective to outsource the *servers* and have your staff still admin and secure them.]]></description>
		<content:encoded><![CDATA[<p>It&#8217;s not just the bandwidth you have to consider, it&#8217;s also the latency. And then, you still have to consider the office&#8217;s bandwidth. If you are outsourcing your internal system databases (CRM, for example) &#8211; then instead of having a gigE connection, you might only have a 30mbps fiber connection. Or maybe only a T1, depending on the size of the company.</p>
<p>Latency though is the major killer. If the company hosting your databases has a fat pipe, and you have a fat pipe, but the hops in between have issues, then you are setting yourself up for mad employees.</p>
<p>IMO, database outsourcing should only be considered as a last resort if your company can&#8217;t justify the expense of hardware and staff to maintain their own datacenter/servers and database software.</p>
<p>It is probably more cost effective to outsource the *servers* and have your staff still admin and secure them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bart Czernicki</title>
		<link>http://blog.sqlauthority.com/2009/05/10/sql-server-10-reasons-for-database-outsourcing/#comment-51906</link>
		<dc:creator><![CDATA[Bart Czernicki]]></dc:creator>
		<pubDate>Fri, 15 May 2009 04:11:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=4885#comment-51906</guid>
		<description><![CDATA[As mentioned above, there is no way a company should allow their data to go into the hands of a third party.  To me that is dangerous and just asking for trouble.

Sure you can have an &quot;agreement&quot; that protects you.  How much is that &quot;agreement&quot; going to protect you overseas?

Think about this...your data gets out and its a PR problem the outsourcing company will lose you as a customer.  You might lose ALL your customers.]]></description>
		<content:encoded><![CDATA[<p>As mentioned above, there is no way a company should allow their data to go into the hands of a third party.  To me that is dangerous and just asking for trouble.</p>
<p>Sure you can have an &#8220;agreement&#8221; that protects you.  How much is that &#8220;agreement&#8221; going to protect you overseas?</p>
<p>Think about this&#8230;your data gets out and its a PR problem the outsourcing company will lose you as a customer.  You might lose ALL your customers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://blog.sqlauthority.com/2009/05/10/sql-server-10-reasons-for-database-outsourcing/#comment-51887</link>
		<dc:creator><![CDATA[Tom]]></dc:creator>
		<pubDate>Thu, 14 May 2009 21:44:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=4885#comment-51887</guid>
		<description><![CDATA[@David &amp; Tim F.  - Clearly anyone doing this is going to have an agreement with the provider to ensure data confidentiality just like you&#039;d have an agreement with an outside contractor if you needed them to come in and do work on your system.  So citing data sensitivity is a pretty weak argument.

As far as performance, I suppose it&#039;s possible you could make enough data transfers to fill up a T3 line but I sincerely doubt it.  Amazon, for example, outsources it&#039;s data in a way (albeit to it&#039;s own data infrastructure) and I suspect they have more transactions per second than any project you&#039;d ever deal with could have.]]></description>
		<content:encoded><![CDATA[<p>@David &amp; Tim F.  &#8211; Clearly anyone doing this is going to have an agreement with the provider to ensure data confidentiality just like you&#8217;d have an agreement with an outside contractor if you needed them to come in and do work on your system.  So citing data sensitivity is a pretty weak argument.</p>
<p>As far as performance, I suppose it&#8217;s possible you could make enough data transfers to fill up a T3 line but I sincerely doubt it.  Amazon, for example, outsources it&#8217;s data in a way (albeit to it&#8217;s own data infrastructure) and I suspect they have more transactions per second than any project you&#8217;d ever deal with could have.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim F</title>
		<link>http://blog.sqlauthority.com/2009/05/10/sql-server-10-reasons-for-database-outsourcing/#comment-51882</link>
		<dc:creator><![CDATA[Tim F]]></dc:creator>
		<pubDate>Thu, 14 May 2009 18:49:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=4885#comment-51882</guid>
		<description><![CDATA[Agree with David - no company would or should willingly allow their sensitive data out of their control for any reason, even to save a few dollars.

The liability alone in doing something like this is insanely huge.

Would be akin to using HoTMaiL as the corporate email system...]]></description>
		<content:encoded><![CDATA[<p>Agree with David &#8211; no company would or should willingly allow their sensitive data out of their control for any reason, even to save a few dollars.</p>
<p>The liability alone in doing something like this is insanely huge.</p>
<p>Would be akin to using HoTMaiL as the corporate email system&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://blog.sqlauthority.com/2009/05/10/sql-server-10-reasons-for-database-outsourcing/#comment-51877</link>
		<dc:creator><![CDATA[David]]></dc:creator>
		<pubDate>Thu, 14 May 2009 15:17:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=4885#comment-51877</guid>
		<description><![CDATA[This is great for small-scale stuff but there is no way you will ever see a large-scale roll out of out-sourced databases.  2 reasons:

1) Sensitive data needs to be in your hands and no one else period.

2) Performance - ie: sucks.]]></description>
		<content:encoded><![CDATA[<p>This is great for small-scale stuff but there is no way you will ever see a large-scale roll out of out-sourced databases.  2 reasons:</p>
<p>1) Sensitive data needs to be in your hands and no one else period.</p>
<p>2) Performance &#8211; ie: sucks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ritesh Shah</title>
		<link>http://blog.sqlauthority.com/2009/05/10/sql-server-10-reasons-for-database-outsourcing/#comment-51740</link>
		<dc:creator><![CDATA[Ritesh Shah]]></dc:creator>
		<pubDate>Sun, 10 May 2009 06:38:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=4885#comment-51740</guid>
		<description><![CDATA[Hi Clair/Pinal,

very nice and informative article. Thanks for sharing it with us. 

Regards,

Ritesh Shah]]></description>
		<content:encoded><![CDATA[<p>Hi Clair/Pinal,</p>
<p>very nice and informative article. Thanks for sharing it with us. </p>
<p>Regards,</p>
<p>Ritesh Shah</p>
]]></content:encoded>
	</item>
</channel>
</rss>

