Comments
Sort by recent activity
(accidental duplicate post) / comments
(accidental duplicate post)
(accidental duplicate post) / comments
(accidental duplicate post)
This is a long standing issue, but I'm not sure Redgate is still updating sql search. I find that repairing my redgate installation solves the problem (from Add/Remove Programs in Windows 10), but temporarily. Note that I am using this version (3.5.0.2590): https://download.red-gate.com/checkforupdates/SQLSearch/SQLSearch_3.5.0.2590.exe / comments
This is a long standing issue, but I'm not sure Redgate is still updating sql search. I find that repairing my redgate installation solves the problem (from Add/Remove Programs in Windows 10), but ...
(accidental duplicate post) / comments
(accidental duplicate post)
I have a different but VERY related problem--I think it's the same cause. I'm using Sql 2008 R2, the early release of sql source control for Git, and a shared dev model (since I'm the only dev):
I have calculated fields in a table which are defined this way:
[OpDtme] AS (dateadd(hour,(6),CONVERT([time](0),[OpDtm],(0)))),
[ClDtme] AS (dateadd(hour,(6),CONVERT([time](0),[ClDtm],(0))))
I commit, then Redgate immediately shows I need to do a new commit because the table designs have changed (they haven't changed). It shows that what it *thinks* it stored in source control is this instead (under "latest source control version" on the right pane):
[OpDtme] AS (dateadd(hour,(6),CONVERT([time](),[OpDtm],(0)))),
[ClDtme] AS (dateadd(hour,(6),CONVERT([time](),[ClDtm],(0))))
Note that redgate has a zero missing after [time] when showing what it thinks it put it in source control. (When I manually check the source control files myself, the zero is there, i.e. the source control files really do match the database.)
When I try to commit again, I get this error back (not surprising since there really have been no changes):
Command:
git commit -a -m "RedgateIssue_NoChange"
Output:
# On branch master
nothing to commit (working directory clean)
Exit code:
1
EDIT: Note I have sent this in to email support, as ticket Red Gate F0044337. / comments
I have a different but VERY related problem--I think it's the same cause. I'm using Sql 2008 R2, the early release of sql source control for Git, and a shared dev model (since I'm the only dev):
I...
Thank you, that was quick. Is the showing of history in ssms with git expected to be added later? Or is that an inherent limitation in git support. / comments
Thank you, that was quick. Is the showing of history in ssms with git expected to be added later? Or is that an inherent limitation in git support.
Is there an estimated release date for GIT support? (even on beta). Thank you. / comments
Is there an estimated release date for GIT support? (even on beta). Thank you.