Comments
Sort by recent activity
I am on Flyway Enterprise, using the desktop client v6.0.0. Flyway Engine: 9.10.2 Git: 2.22.0 Redgate Compare: 1.6.0.7305 / comments
I am on Flyway Enterprise, using the desktop client v6.0.0.Flyway Engine: 9.10.2Git: 2.22.0Redgate Compare: 1.6.0.7305
Is there a possible way to tell SQL Monitor to ignore the database replicatedmaster? It's only there for a blip of time, so I can't select it from any list. / comments
Is there a possible way to tell SQL Monitor to ignore the database replicatedmaster? It's only there for a blip of time, so I can't select it from any list.
Got another disconnect last night, so a little over a week this time before it un-auth'd the user: [image] [image] Maybe it's something we can work around or tell it to not attempt to connect to? / comments
Got another disconnect last night, so a little over a week this time before it un-auth'd the user:Maybe it's something we can work around or tell it to not attempt to connect to?
following a dbcc checkdb on every database, all we get is this on every database: CHECKDB found 0 allocation errors and 0 consistency errors in database '<dbname>'. So it doesn't look like there's any corruption; at least at the current time. It might be a bit tricky to figure out if there somehow becomes a tiny bit of corruption at the time of disconnect. / comments
following a dbcc checkdb on every database, all we get is this on every database:CHECKDB found 0 allocation errors and 0 consistency errors in database '<dbname>'.So it doesn't look like there's an...
One suggestion I might have: Would it be possible to build some sort of "auto-retry" mechanism for when this happens? / comments
One suggestion I might have:Would it be possible to build some sort of "auto-retry" mechanism for when this happens?
ATurner said:
Hi Tom This issue should be fixed in 11.1.8
Do we have a ETA on the release date for this update? / comments
ATurner said:
Hi TomThis issue should be fixed in 11.1.8
Do we have a ETA on the release date for this update?
ATurner said:
Hi Tom I believe this to be related to a known bug. I shall let you know once there is a fix available.
Could you include me in on this fix? I'm getting this same issue. / comments
ATurner said:
Hi TomI believe this to be related to a known bug. I shall let you know once there is a fix available.
Could you include me in on this fix? I'm getting this same issue.
Working workaround for me: After exec'ing a fake table on vwName I moved the Insert into an exec of it's own and works as the bypass. EXEC('INSERT INTO vwName(columns) VALUES(data)') / comments
Working workaround for me:After exec'ing a fake table on vwName I moved the Insert into an exec of it's own and works as the bypass. EXEC('INSERT INTO vwName(columns) VALUES(data)')
If this isn't going to get added any time soon, could we at least get a guide of how to update the SQLCover ourselves? / comments
If this isn't going to get added any time soon, could we at least get a guide of how to update the SQLCover ourselves?
So i figured out what the issue was on my end.
It looks like if you have conflicting commits, you can't tell it to deselect everything. / comments
So i figured out what the issue was on my end.
It looks like if you have conflicting commits, you can't tell it to deselect everything.