﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Reporting Services / Reporting Services 2008 Administration  / Migrating VSS to SVN for SSIS and SSRS projects, looking for advice and best practices/experiences... / Latest Posts</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, 20 Jun 2013 01:11:14 GMT</lastBuildDate><ttl>20</ttl><item><title>Migrating VSS to SVN for SSIS and SSRS projects, looking for advice and best practices/experiences...</title><link>http://www.sqlservercentral.com/Forums/Topic1379860-1632-1.aspx</link><description>HelloWe are planning on migrating (keeping history) our existing VSS to SVN. We have SSRS, SSIS projects and SQL to move.Can I use VSSAnalyze on a specific folder rather than the entire DB?Regarding the structure in SVN  (I can’t see the need for branching) for these types of projects so I’m thinking a simple structure like:Reporting.SSIS ..Project 1..Project 2.SSRS..Project 1..Project 2.SQL..DB1...Functions		...Procedures...Triggers..DB2...Functions		...Procedures...TriggersAny thoughts, suggestions and warnings are appreciated.</description><pubDate>Thu, 01 Nov 2012 08:43:57 GMT</pubDate><dc:creator>d_george</dc:creator></item></channel></rss>