How can we help you today? How can we help you today?
StephanieHerr
Activity overview Badges (0) Posts (39) Comments (134)

Comments

Sort by recent activity
Hello Jim, We realize that a lot of users work in a shared database model and hope to offer better support for this model in a future version. We considered sharing the same set of "internal working files" across all the developers, but this can lead to a few problems because you could actually connect to the database from SSMS on another machine and then you might not have access to these "internal working files." Another reason is SQL Source Control does not make any changes to the database. Therefore, there's no way for us to know if a different user has linked the database to source control or not. There are probably some other issues that we'll hit when we start to work on supporting this better. For now, linking the db is a one time thing, so I hope that is not too hard for each developer to do. If you have SSMS on a laptop and a desktop, you'll have to link each of these seperately because again, the "internal working files" are not shared. On a shared db model, getting latest doesn't really make sense unless changes are made directly to the source control system or committed externally. In most of these cases, as the development continues, these will disappear from the different lists once everything is in synch. The issues are definitely caused by the "internal working files" being out of synch. The more often users visit the commit tab, the less likely this will happen. For now, I hope you can just ignore some of these descrepancies and just concentrate on committing the objects that you have made changes too. I'm glad you found our recommendations post. I hope it helped. Thank you! Stephanie M. Herr :-) SQL Source Control - Project Manager / comments
  1. Community
  2. SQL Source Control EAP
  3. SQL Source Control Storing Files for Each User Account
Hello Jim, We realize that a lot of users work in a shared database model and hope to offer better support for this model in a future version. We considered sharing the same set of "internal workin...
0 votes
If anyone has any concerns about switching from a shared model to a dedicated model, please post here or contact us at support@red-gate.com. We would really like to discuss these concerns. / comments
  1. Community
  2. SQL Source Control EAP
  3. Development and Deployment Recommendations
If anyone has any concerns about switching from a shared model to a dedicated model, please post here or contact us at support@red-gate.com. We would really like to discuss these concerns.
0 votes
This error occurs because we currently don't support the SQL Server 2008 DATA_COMPRESSION keyword. We will be looking into this soon. For now, you would need to turn off the data compression on your tables to work with SQL Source Control. We'll update this posting once this is supported. You can vote/comment on this feature in our Suggestion Forum at http://redgate.uservoice.com/forums/390 ... ?ref=title Thank you! Stephanie M. Herr :-) SQL Source Control - Project Manager / comments
  1. Community
  2. SQL Source Control EAP
  3. Error Committing a New Database - Unexpected Token 'PAGE'
This error occurs because we currently don't support the SQL Server 2008 DATA_COMPRESSION keyword. We will be looking into this soon. For now, you would need to turn off the data compression on yo...
0 votes
We have tested against the 2008 R2 RC, which works. We are currently configuring a 2008 R2 RTM server to test against. If SSMS is open during the install, then you will need to re-start SSMS before you can start using SQL Source Control. I saw your email that you got it working now, so maybe re-starting was the issue??? I'm glad it is working for you now. Thanks! Stephanie M. Herr :-) SQL Source Control - Project Manager / comments
  1. Community
  2. SQL Source Control EAP
  3. Installing on 2008 R2 RTM
We have tested against the 2008 R2 RC, which works. We are currently configuring a 2008 R2 RTM server to test against. If SSMS is open during the install, then you will need to re-start SSMS befor...
0 votes
Hi Jim, Recovering the working base should let you continue. I'm glad everything seems to be ok. Please get in touch if you experience any additional problems. It seems like you are using SVN. This problem could occur if any subversion operations where performed outside of our tool on the working base, C:\Users\Jim Fennell\AppData\Local\Red Gate\SQL Source Control 0\WorkingBases. Do you know if any SVN operations were performed on these folders? Thank you for your help! Stephanie M. Herr :-) SQL Source Control - Project Manager / comments
  1. Community
  2. SQL Source Control EAP
  3. Working Base is Broken
Hi Jim, Recovering the working base should let you continue. I'm glad everything seems to be ok. Please get in touch if you experience any additional problems. It seems like you are using SVN. T...
0 votes
I just wanted to clarify that we are NOT supporting SSMS 2008 Express. We can prevent SQL Source Control from loading in SSMS 2005 Express, but we can NOT prevent it in 2008 Express. It may work, but unfortunately, if there are any issues we will NOT be able to support them at this time. The supported versions can be found on our website at http://www.red-gate.com/Products/SQL_Source_Control and then select "Requirements and prerequisites" on the right. Thank you! Stephanie M. Herr :-) SQL Source Control - Project Manager / comments
  1. Community
  2. SQL Source Control EAP
  3. Compatilble with SQL Server Management Studio 2008 Express?
I just wanted to clarify that we are NOT supporting SSMS 2008 Express. We can prevent SQL Source Control from loading in SSMS 2005 Express, but we can NOT prevent it in 2008 Express. It may work, ...
0 votes
Thank you for emailing the files. We are looking into this now. Our internal reference number is SOC-1020. / comments
  1. Community
  2. SQL Source Control EAP
  3. Error trying to apply updates to Trigger from TFS to DB
Thank you for emailing the files. We are looking into this now. Our internal reference number is SOC-1020.
0 votes
Hello, To answer your last question, the "trial period" for SQL Source Control will be 28 days. So, after installing the full release version, you will have 28 days to evaluate the software. Thank you! Stephanie M. Herr :-) Project Manager - SQL Source Control / comments
  1. Community
  2. SQL Source Control EAP
  3. Purchasing SQL Source Control upon Release
Hello, To answer your last question, the "trial period" for SQL Source Control will be 28 days. So, after installing the full release version, you will have 28 days to evaluate the software. Thank...
0 votes
We haven't seen this, but doing a quick Google search, it seems to be a permission thing with Subversion. It looks like you need to add the following line to your authz file. * = r Google hits: http://geekgok.blogspot.com/2009/01/svn ... dable.html http://sdesmedt.wordpress.com/2006/11/0 ... ubversion/ Please let us know if this doesn't work. Thank you! Stephanie M. Herr :-) SQL Source Control - Project Manager / comments
  1. Community
  2. SQL Source Control EAP
  3. Item is not readable
We haven't seen this, but doing a quick Google search, it seems to be a permission thing with Subversion. It looks like you need to add the following line to your authz file. * = r Google hits:http...
0 votes
Hello, Just to note, SQL Source Control is still in an early access phase and we do not recommend using it on Production DBs. Your situation is kind of unique since you do not have a dev db... I don't understand exactly what you are trying to do. :-) It sounds like you are using Visual Studio and editing the CREATE script files directly. The whole purpose of SQL Source Control is that you can continue to work directly on your db within SQL Server Management Studio, so that you don't have to worry about the CREATE scripts and SQL Source Control generates them for you. If you do make a change in VS and commit it, then you should see this on the Get Latest tab and you can click the "Get Latest" button to update the db. What do you mean that you cannot "Get Latest?" Please be careful that the SQL syntax within the script is correct. This is why it is better to just work directly on the db. It's true that changes to the db do not automatically get committed to source control. This requires discipline from the db developer to commit the change. We would like them to supply a comment when commiting so others can understand why they made the change. SQL Source Control helps by placing blue indicators on the ObjExp, which reminds you that you have made changes that you haven't commited yet. You can use SQL Compare Pro to automatically check that your production db is at the version you expect it to be. This is retroactive, but allows you to see if any changes are made directly to prod that were not expected. These changes can then be applied back to your dev db and committed to source control if that's what is decided. I hope this helps! Please let me know if you are still having problems getting changes from TFS to your db. Thank you! Stephanie M. Herr :-) SQL Source Control - Project Manager / comments
  1. Community
  2. SQL Source Control EAP
  3. TFS 2008
Hello, Just to note, SQL Source Control is still in an early access phase and we do not recommend using it on Production DBs. Your situation is kind of unique since you do not have a dev db... I do...
0 votes
Total activity
266
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
93