Comments
Sort by recent activity
Downloaded SQL Toolbelt installer today, and it did not update to 4.3.20209 Downloaded the extension from VS Marketplace per the link, and it did update to 20209: Using SQL Change Automation version: 4.3.20209.21516 Still getting the Newtonsoft.Json error: C:\Projects\database\SQLCore\PrimeReporting\PrimeReporting.sqlproj: Error: : Could not load file or assembly 'Newtonsoft.Json, Version=12.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The system cannot find the file specified.: Could not load file or assembly 'Newtonsoft.Json, Version=12.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The system cannot find the file specified. / comments
Downloaded SQL Toolbelt installer today, and it did not update to 4.3.20209Downloaded the extension from VS Marketplace per the link, and it did update to 20209:Using SQL Change Automation version:...
Running into the same error while attempting to deploy pending scripts. Using SQL Change Automation version: 4.3.20205.21469 Error: : Could not load file or assembly 'Newtonsoft.Json, Version=12.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The system cannot find the file specified.: Could not load file or assembly 'Newtonsoft.Json, Version=12.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The system cannot find the file specified.
/ comments
Running into the same error while attempting to deploy pending scripts.Using SQL Change Automation version: 4.3.20205.21469Error: : Could not load file or assembly 'Newtonsoft.Json, Version=12.0.0...
It's not the first deployment to this database, both __MigrationLog and __SchemaSnapshot exist in the database and have data in them. / comments
It's not the first deployment to this database, both __MigrationLog and __SchemaSnapshot exist in the database and have data in them.
WARNING: C:\Windows\TEMP\DLM Automation\4cbf3sqa.5cl\PrimeReporting.sqlproj: No schema snapshot could be retrieved from the target database; no report will be generated until your next deployment. If you continue to see this message, then it is possible that a schema snapshot file is not being created during build. To resolve, specify the ShadowServer property in your build configuration. See https://www.red-gate.com/sca/continuous-integration / comments
WARNING: C:\Windows\TEMP\DLM Automation\4cbf3sqa.5cl\PrimeReporting.sqlproj: No schema snapshot could be retrieved from the target database; no report will be generated until your next deployment. ...
This is not the first deployment. / comments
This is not the first deployment.
That's the frustrating thing about the way the Nuget team handled this- it's a subtle problem that will continue to creep through the ecosystem, randomly breaking processes as the tools are updated. I'm sure eventually I'll update my ProGet server to find half of my deployment processes failed due to SemVer normalization. / comments
That's the frustrating thing about the way the Nuget team handled this- it's a subtle problem that will continue to creep through the ecosystem, randomly breaking processes as the tools are updated...
The nuget team forced SemVer as the standard a few years ago, and has no desire to roll it back: https://github.com/NuGet/Home/issues/3050 / comments
The nuget team forced SemVer as the standard a few years ago, and has no desire to roll it back: https://github.com/NuGet/Home/issues/3050
AshaPatel said: The last thing you should do is make changes due to the opinions of the outspoken few - this is why we rely on uservoice, it allows us to get a much more general view of consensus.
Wow. Was there a User Voice item asking for "Match whole words only" to replace "Exact Match"??? Seems like some outspoken few at RedGate decided to make this change. I'd love to see the "Use cases" where this is an improvement. For me, this is not an improvement. I've inherited a large set of stored procedures that contain things like: Exec Systemx.dbo.QueueEmail @Subject N'Failed to import from source' So a user sends me an email pointing out a problem, and I need to find where this is being generated from. SQL Search to the rescue? Nope. Searching "Failed to import from source" with 'Match whole words only' fails, because N' is considered as part of the word. Removing match whole words only produced a lot of noise. Lucky for me, I dump everything into git so I can use an external tool to search. (good thing it's not hung up words) / comments
AshaPatel said:The last thing you should do is make changes due to the opinions of the outspoken few - this is why we rely on uservoice, it allows us to get a much more general view of consensu...
So I applied a filter to the pipeline to ignore Assembly changes, and after restarting the DLM Monitor services, I was able to acknowledge the drift. / comments
So I applied a filter to the pipeline to ignore Assembly changes, and after restarting the DLM Monitor services, I was able to acknowledge the drift.
I'm having the same issue, DLM Dashboard 1.7.5.1116
It's only one of a dozen pipelines that fail to render.
Chrome is running hard on that tab, 36% CPU and 2gb of ram, then it eventually reloads.
One thing I noticed for this pipeline is that there's CLR objects that are trying to show a diff. / comments
I'm having the same issue, DLM Dashboard 1.7.5.1116
It's only one of a dozen pipelines that fail to render.
Chrome is running hard on that tab, 36% CPU and 2gb of ram, then it eventually reloads.
O...