tag:blogger.com,1999:blog-6082242.post112609544288440974..comments2023-08-06T11:15:28.003+01:00Comments on JBlogs: Automated SQL Server database objects scripting and deployment in continuous integration environmentUnknownnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6082242.post-15047157304217633702007-08-07T08:27:00.000+01:002007-08-07T08:27:00.000+01:00Sorry being hugely late...I think it will only be ...Sorry being hugely late...<BR/>I think it will only be possible if SQL Server Enterprise Manager keeps a version information of sprocs.Jingyehttps://www.blogger.com/profile/08537823731513415471noreply@blogger.comtag:blogger.com,1999:blog-6082242.post-80270462558017437072007-07-20T20:23:00.000+01:002007-07-20T20:23:00.000+01:00This information is very helpful to a project i'm ...This information is very helpful to a project i'm currently working on. I just have one question for you. <BR/><BR/>We're using source control (Surround SCM) to check-in stored procedures from dev databases (SQL Server Enterprise Manager). Then during the build process, doing a GET of these sprocs and copying them to the corresponding production databases.<BR/><BR/>Is there a way to ONLY check-in sprocs that have been created/updated since the last check-in? If there is, is it possible to do a GET of only these created/updated sprocs and copy those to prod database, thus not effecting the sprocs that were not changed and saving vast amounts of time during the build process?<BR/><BR/>Thanks,<BR/>LukeAnonymousnoreply@blogger.com