Hi guys'n'girls...
I currently work for a company where we develop several large ASP.NET applications which are VERY data centric. But lately we have run into a problem on our developer DB...
On the project I am working on we currenctly have approx. 10 developers working concurrently on the database. That means that we often run into errors caused by two developers working on the same stored procedure, function or trigger so the developer who adds his changes last, overwrites the modifications done by the other developer. The obvious answer is source control for the db, but as far as I can tell this is only available for stored procedures and not for functions or triggers... And even the stored procedure solution isn't very safe because it only works if every developer is editing the procedures through VS.
So what do we do? There must be some solution to this problem... And I'm pretty convinced that we are not the first company to face this problem. Are we doing it the wrong way or do you know another solution?
Thanks in advance!
Try these two urls for options but the manual way to do it is to leave the DDL coding to one or two developers working together and run a stored proc to eliminate duplicates. Hope this helps.
http://www.allisonfamily.org/bill/library/articles/vss-sql-howto/
http://www.sqlservercentral.com/products/bwunder/archiveutility/
No comments:
Post a Comment