Comments
Sort by recent activity
Hello Jim,
This is very strange...
We are using SQL Compare to commit/get. SQL Compare sometimes requires the table to be rebuilt, but this doesn't sound like your situation.
Would you be able email us a copy of what's in source control and a SQL Compare snapshot of your database so we can reproduce the problem here? This will only be used for our internal testing.
Email: support@red-gate.com
Internal Reference Number: SOC-1235
Thank you!
Stephanie M. Herr :-)
Project Manager - SQL Source Control / comments
Hello Jim,
This is very strange...
We are using SQL Compare to commit/get. SQL Compare sometimes requires the table to be rebuilt, but this doesn't sound like your situation.
Would you be able ema...
Hello,
Thank you for reporting this issues. The first issue is definitely a bug. Our internal reference number is SOC-1163. This will not be fixed for v1, but you can just exit out of the help bubble.
For number 2, please vote/comment on these suggestions:
- A "Recent Messages" Button for Comments Like on TSVN
- Commit check in comment needs to be larger
Thank you!
Stephanie Herr :-)
Project Manager - SQL Source Control / comments
Hello,
Thank you for reporting this issues. The first issue is definitely a bug. Our internal reference number is SOC-1163. This will not be fixed for v1, but you can just exit out of the help b...
FYI - The first issue of the bubble being shown when canceling the link has been fixed in the v1.0.3.73 patch release. More info about this release is available at http://www.red-gate.com/messageboard/vi ... hp?t=11447. / comments
FYI - The first issue of the bubble being shown when canceling the link has been fixed in the v1.0.3.73 patch release. More info about this release is available at http://www.red-gate.com/messageb...
We have fixed this problem in the latest release. Please install http://downloads.red-gate.com/beta/SQLS ... 0.1.11.exe
Thank you to everyone who submitted an exception report! It helped us diagnose the issue and get this fix turned around very quickly.
Thanks again!
Stephanie M. Herr :-)
Project Manager - SQL Source Control / comments
We have fixed this problem in the latest release. Please install http://downloads.red-gate.com/beta/SQLS ... 0.1.11.exe
Thank you to everyone who submitted an exception report! It helped us diagn...
Hello,
In order to replicate this issue, could you please post or email support@red-gate.com the script for dbo.udf_UserDetails?
If by email, please reference our internal support number SOC-1197.
Thank you! Stephanie M. Herr :-)
Project Manager / comments
Hello,
In order to replicate this issue, could you please post or email support@red-gate.com the script for dbo.udf_UserDetails?
If by email, please reference our internal support number SOC-1197.
...
Hello,
Are you using Win7 x64? This is a known issue (SOC-675) on this OS...
The upgrade completed successfully, but you won't be able to use the new version until you restart SSMS. If you restart, and then select Help on the SQL Source Control tab > About, could you verify that your version is v0.4.1.2?
FYI - To reinstall, you can uninstall SQL Source Control from Add/Remove Programs and then download the latest version from the announcement posted at the top of this forum.
Thank you for the feedback. This is only an issue on Win7 x64, which we hope to fix at some point. On all other OSs, you are prompted to close SSMS yourself and you can not install until you do so. On Win7 x64, it just tries to close SSMS by itself without warning you.
It may be best on the "Check for Updates" to click the "more information" link. This will bring you to a page with the download link. You can then close SSMS and start the download. I know this is kind of an awkward workaround for now, but at least you can be sure that there won't be any problems with the update.
Thank you so much for reporting this! I hope this information helps.
Stephanie M. Herr :-)
SQL Source Control - Project Manager / comments
Hello,
Are you using Win7 x64? This is a known issue (SOC-675) on this OS...
The upgrade completed successfully, but you won't be able to use the new version until you restart SSMS. If you restar...
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
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...
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
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.
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
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...
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
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...