Yeah, I have tried SVN, Git, Mercurial, TFS... all of them. They are all good for code.
But from my own personal experience, I find that people tend to not place their stored procedures under version control. They seem to see them as separate from all the other C# source code and what not. It can be quite hard to get a team to use version control for their stored procedures. In fact, without trying to hijack anyone's thread (since it is related), it would be good to find out what other experts in here do to version control their stored procedures. On 26 April 2012 15:53, Stephen Russell <[email protected]> wrote: > On Wed, Apr 25, 2012 at 8:33 AM, Reuben Bartolo > <[email protected]> wrote: > > Stored procedures, as everyone mentioned, have huge advantages, and it is > > recommended that you use them whenever possible. However, a disadvantage > > that few speak about, is how to keep them in version control. > --------------- > > Have you tried <http://subversion.apache.org/> > > > > > -- > Stephen Russell > Sr. Analyst > Ring Container Technology > Oakland TN > > 901.246-0159 cell > > -- > You received this message because you are subscribed to the Google > Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML > Web Services,.NET Remoting" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/dotnetdevelopment?hl=en?hl=en > or visit the group website at http://megasolutions.net > -- You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/dotnetdevelopment?hl=en?hl=en or visit the group website at http://megasolutions.net
