<?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: Using Visual SourceSafe &#8211; How to version control SQL Server Stored Procedures with Visual Studio 2003</title>
	<atom:link href="http://www.kevingao.net/sourcesafe/how-to-version-control-sql-server-stored-procedures-using-sourcesafe-and-visual-studio-2003.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.kevingao.net/sourcesafe/how-to-version-control-sql-server-stored-procedures-using-sourcesafe-and-visual-studio-2003.html</link>
	<description>SourceSafe, Source Control, Software Development</description>
	<lastBuildDate>Fri, 10 Sep 2010 13:50:09 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: &#187; Using Visual SourceSafe &#8211; Integrating VSS with SQL Server 2005</title>
		<link>http://www.kevingao.net/sourcesafe/how-to-version-control-sql-server-stored-procedures-using-sourcesafe-and-visual-studio-2003.html/comment-page-1#comment-2722</link>
		<dc:creator>&#187; Using Visual SourceSafe &#8211; Integrating VSS with SQL Server 2005</dc:creator>
		<pubDate>Wed, 08 Sep 2010 03:29:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.kevingao.net/?p=499#comment-2722</guid>
		<description>[...] Similar to SSMS 2008, we cannot version control SQL objects directly in SSMS 2005. However, we can create scripts for the database and all its objects, save them to a solution and then add the solution to source control. For more details, please refer to another article: How to add SQL Server 2005/2008 Stored Procedures to VSS. [...]</description>
		<content:encoded><![CDATA[<p>[...] Similar to SSMS 2008, we cannot version control SQL objects directly in SSMS 2005. However, we can create scripts for the database and all its objects, save them to a solution and then add the solution to source control. For more details, please refer to another article: How to add SQL Server 2005/2008 Stored Procedures to VSS. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EdwardC</title>
		<link>http://www.kevingao.net/sourcesafe/how-to-version-control-sql-server-stored-procedures-using-sourcesafe-and-visual-studio-2003.html/comment-page-1#comment-2655</link>
		<dc:creator>EdwardC</dc:creator>
		<pubDate>Wed, 18 Aug 2010 02:16:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.kevingao.net/?p=499#comment-2655</guid>
		<description>Hi,

  I can&#039;t find Tools -&gt; Options -&gt; Database Tools -&gt; Server Explorer in VS 2008. How do I achieve the same in VS 2008?</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>  I can&#8217;t find Tools -&gt; Options -&gt; Database Tools -&gt; Server Explorer in VS 2008. How do I achieve the same in VS 2008?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Akbar</title>
		<link>http://www.kevingao.net/sourcesafe/how-to-version-control-sql-server-stored-procedures-using-sourcesafe-and-visual-studio-2003.html/comment-page-1#comment-1702</link>
		<dc:creator>Akbar</dc:creator>
		<pubDate>Mon, 26 Jan 2009 16:31:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.kevingao.net/?p=499#comment-1702</guid>
		<description>Hi,
can we integrate sqlserver 2000 with visual studio 2005 the same way.
as in the 2005 configuration there is nothing related to versioning of stored procs.

thanks</description>
		<content:encoded><![CDATA[<p>Hi,<br />
can we integrate sqlserver 2000 with visual studio 2005 the same way.<br />
as in the 2005 configuration there is nothing related to versioning of stored procs.</p>
<p>thanks</p>
]]></content:encoded>
	</item>
</channel>
</rss>
