How can we help you today? How can we help you today?
ceacl
Activity overview Badges (0) Posts (4) Comments (8)

Activity overview

Latest activity by ceacl

Yes, thats exactly what I was asking for. I just didn't take the time to look up in the corner and had it in my head that it should be a button similar the one toward the bottom of the page. Very good. Thanks for the response. / comments
  1. Community
  2. SQL Compare Previous Versions
  3. SSMS Integration Pack Suggestion
Yes, thats exactly what I was asking for. I just didn't take the time to look up in the corner and had it in my head that it should be a button similar the one toward the bottom of the page. Very g...
0 votes
SSMS Integration Pack Suggestion
  1. Community
  2. SQL Compare Previous Versions
Not sure if it was done this way because of licensing but it would be nice to have access to both Schema and Data on one menu/page rather than separate. More times than not when I do a Schema compa...
2 followers 3 comments 0 votes
I didn't see any other threads related to issues with this new release so I hope this is the proper place to post. When I click on the database in SSMS and choose the new Schema Compare / Deploy or Data Compare / Deploy the sub-menus that says Set as Source and Set as Target gets cut off on the right hand side. It seems that the sub-menu container is not wide enough to display the text. Not a huge issue but I thought I'd bring it to your attention. Very cool integration by the way! / comments
  1. Community
  2. SQL Source Control Previous Versions
  3. SQL Source Control now integrated with SQL Compare
I didn't see any other threads related to issues with this new release so I hope this is the proper place to post. When I click on the database in SSMS and choose the new Schema Compare / Deploy or...
0 votes
I too received the Refactor errors after installing Prompt 5. As suggested above I uninstalled both Refactor and Prompt 4 however they both still appear on the SSMS menu. Any recommendation on how to fully uninstall and remove them from SSMS? / comments
  1. Community
  2. SQL Prompt 5 EAP
  3. Uninstall SQL Refactor before installing SQL Prompt 5
I too received the Refactor errors after installing Prompt 5. As suggested above I uninstalled both Refactor and Prompt 4 however they both still appear on the SSMS menu. Any recommendation on how...
0 votes
just updated to 0.3.1.3 and am getting the same error on some but not all databases. My coworker is getting them on other databases that work for me and vice versa. Failed to update: System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 783, offset:30 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 779, offset:56 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 808, offset:41 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1347, offset:152 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1625, offset:0 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1371, offset:26 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 800, offset:0 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 799, offset:78 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1285, offset:11 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 669, offset:130 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1861, offset:110 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1705, offset:18 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 247, offset:38 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 251, offset:38 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1543, offset:224 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1858, offset:63 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1542, offset:99 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1541, offset:60 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1080, offset:31 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1077, offset:0 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1774, offset:0 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1691, offset:117 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 169, offset:11 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 216, offset:137 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 522, offset:26 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1933, offset:18 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1727, offset:32 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1728, offset:36 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1885, offset:43 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1167, offset:500 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 366, offset:21 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1171, offset:115 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1173, offset:22 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1147, offset:13 --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- --- End of inner exception stack trace --- at RedGate.SQLSourceControl.CommonUI.Forms.ErrorDialog.DoWithObviousExceptionsThrowAll(Action action) at #JLc.#PLc.#CTc(ICancellableOperation`1 operation, Object token) / comments
  1. Community
  2. SQL Source Control EAP
  3. ERR: PathToLongException when "commit changes" clicked
just updated to 0.3.1.3 and am getting the same error on some but not all databases. My coworker is getting them on other databases that work for me and vice versa. Failed to update: System.IO.Pat...
0 votes
Conflict on coworks workstation but not on mine
  1. Community
  2. SQL Source Control EAP
We have a team of 4 developers using this tool in a shared DB environment and are experincing Conflict issues quite frequently even though the conflicted object(s) in question had not been changed ...
1 follower 1 comment 0 votes
Changing Order for Columns in a Table
  1. Community
  2. SQL Source Control EAP
Should changing the order of columns in a table trigger an edit? We made no other changes to the table except to the column order and expected to see a triggered edit. The tool did not recognize t...
1 follower 1 comment 0 votes
Is this what youre looking for? C:\Documents and Settings\<USER>\Local Settings\Application Data\Red Gate\SQL Source Control 0\WorkingBases This is under XP. May be diff if youre running Vista or Win7 / comments
  1. Community
  2. SQL Source Control EAP
  3. Where is the version information stored?
Is this what youre looking for? C:\Documents and Settings\<USER>\Local Settings\Application Data\Red Gate\SQL Source Control 0\WorkingBases This is under XP. May be diff if youre running Vista or ...
0 votes
Think of your repository as a snapshot of your system at any given time. Like a timeline. When you drop an object and commit that drop to the repository your HEAD (latest) revision will not contain that object definition and therefore represents the current state of your system. If you want to travel back in time to before the object was dropped you can certainly do that in any number of ways. My preferred choice is to use TortoiseSVN to either browse to a previous revision in the repository or browse to the object in question using TortoiseSVN browser and do a Show Log. This method shows a complete history of changes made to that object. Anything that gets committed to your repository is there forever. There is no way to delete it from the repository short of deleting the entire repository. You may not see the object definitions you deleted if you're looking at the HEAD revision but you can see it if you go back in time to a prior revision. Hope that helps. / comments
  1. Community
  2. SQL Source Control EAP
  3. Dropped objects just disappear
Think of your repository as a snapshot of your system at any given time. Like a timeline. When you drop an object and commit that drop to the repository your HEAD (latest) revision will not conta...
0 votes
Install fails
  1. Community
  2. SQL Source Control EAP
Attempting to install this on a 64bit Vista machine. The install appears to complete however when it reaches the end of the progress bar the follow error is presented. SQL Source Control 0.2 | In...
1 follower 1 comment 0 votes
Total activity
20
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
8