Comments
2 comments
-
Hello,
Thanks for your question on SQL Source Control. We've opened up a support ticket to work on this issue as I will need to get some other team members to address different parts of the question. I'll be responding in the ticket right after finishing this post. -
It would help if we could know if it's possible to have multiple changelog databases per database server. We have one server that stores multiple environments (Alpha, Beta, Staging, etc.) and we want some of those databases in the LKP table to use the normal RG sprocs to identify changes based on the tracelog, while others should use our sproc to fetch change information from the TFS Warehouse database.
Is there somehow a method to specify a server for a changelog database in the XML? For example: <TraceCacheDatabase>sql-server.alpha.ourwebsite.com,4001:ChangeLog</TraceCacheDatabase>
Add comment
Please sign in to leave a comment.
However, this information doesn't tend to always be accurate, because someone may modify an object in the database but may not check in that change. We are more interested in times that developers check in a change, because it will be on it's way to our Production environment.
Our plan is to modify the stored procedures dbo.RG_WhatsChanged_v3 and dbo.RG_WhatsChanged_v4 to get from our TFS Warehouse database, a list of developers by their check-ins into TFS Source Control. Before we take on this effort, we would like to know if there is a built-in method for switching the Logging Database to populate from somewhere else? Should we know anything before taking on this work? Do the _v1, _v3 and _v4 appends on the sprocs relate to the SQL Source Control versions?
Many thanks in advance!