Activity overview
Latest activity by wesleysmith
Does not detect change relating to "GRANT REFERENCES"
Using SQL Source Control 2.0.10.11:
I ran this command in SQL:GRANT CREATE PROCEDURE to [sql_dependency_starter]
GRANT CREATE QUEUE to [sql_dependency_starter]
GRANT REFERENCES o...
I have seen this case happen when I've selected just one object that only I have been working on, so I don't think it's a case of selecting other people's changes. / comments
I have seen this case happen when I've selected just one object that only I have been working on, so I don't think it's a case of selecting other people's changes.
Identifying which user made the changes
After installing the version 2 EAP, I have relinked my database to TFS, and told SQL Source Control that I'm using a Shared database. In general, it works okay, but whenever I go to check in a cha...
Unlinking and relinking the database seems to have solved the problem. Let me know if you'd like the log file to investigate further. / comments
Unlinking and relinking the database seems to have solved the problem. Let me know if you'd like the log file to investigate further.
SQL Source Control hangs while "Determining latest version"
Version 2.0.0.37
Linked to TFS server
Using Shared Model
SSMS 2008 R2
I have a database that I have previously linked to TFS. Today, when I start up SSMS select my database, and choose "Commit Cha...
I wonder how you propose to handle data changes with the dedicated model. For example, consider a case where I update my database to change the name of a column from "LocalTime" to "UTCTime". At the same time, I run a script to update all existing rows to add 8 hours. SQL Source Control will notice the name of the column has changed, and will check in that change to source control. But when other developers get my changes, they'll only get the column name change, not the data update. Similar examples include moving a column from one table to another (while preserving data). A similar issue would exist when adding a non-nullable column (with no default) to a table - in that case the update to the other dev databases would likely just fail. There are even some cases where the change involves no schema change - for example, stripping out trailing spaces from all rows of a table.
I realize that these problems aren't new - they exist even with the shared model when you need to take your changes from Dev to Test. But with the dedicated model, it seems that the problem is made worse because now you have so many copies of Dev databases that need updating.
It seems like a possible fix would be the ability to attach update scripts along with the schema changes, but even then you have problems with proper ordering, etc.
I realize this is a difficult problem to solve, but I wonder what your suggestions, thoughts, or best practices are on this matter. / comments
I wonder how you propose to handle data changes with the dedicated model. For example, consider a case where I update my database to change the name of a column from "LocalTime" to "UTCTime". At ...
Simon,
Your workaround appears to have worked perfectly, and all is working again.
Thank you,
Wesley / comments
Simon,
Your workaround appears to have worked perfectly, and all is working again.
Thank you,
Wesley
Crash after trying to reconnect to a (moved) TFS repository
I had SQL Source control version 0.3.1.3 working just fine. Then, I decided I needed to move the location of the SQL directory in the TFS (2005) repository. I disconnected SQL Source Control, the...