How can we help you today? How can we help you today?
StephanieHerr
I emailed FatherJack directly to discuss 2nd bullet point in first post, performance issues, parsing problems (need sample file), and current situation on commit/get latest tabs, which seems to be completely stuck... / comments
I emailed FatherJack directly to discuss 2nd bullet point in first post, performance issues, parsing problems (need sample file), and current situation on commit/get latest tabs, which seems to be ...
0 votes
There's another situation that could cause this issue. It could happen if you commit an object, but do not commit its dependencies. This causes the version in source control to be in an invalid state, which we then have trouble parsing. You should be warned if there are dependencies when committing or getting and it is checked by default to include these. Creating a new db and relinking does NOT help in this case. WORKAROUND: 1) If you don’t have a lot of history in source control that you care about since this is an evaluation, then it might be better to just DELETE everything in source control and start again. This time when you commit an object, include its dependencies and hopefully you will get pass this issue. 2) If you want to keep your current history, do you have SQL Compare Pro? If so, you could script TableA to a scripts folder and then commit this to the Tables directory in SVN using TortoiseSVN. This should put the source control version back in a “valid†state and let you continue. If you don’t have SQL Compare Pro, script out the table using SSMS, and then Commit to SVN, but make sure it is named owner.tablename.sql like the other files are named. / comments
There's another situation that could cause this issue. It could happen if you commit an object, but do not commit its dependencies. This causes the version in source control to be in an invalid s...
0 votes