Comments
Sort by recent activity
I have gotten this error as well. When I finally found the problem, the error wasn't in the snippets file for ADS at all. It was actually in the SSMS snippets file that it was trying to import from. In my case there was a a character sequence that in the XML file that, when copied over to JSON, messed up the JSON parsing. I cannot remember exactly what the sequence was, but I think it was because I had a double-quote (") in one of the XML nodes of the snippet file. You might check that to see if that solves your issue(s). / comments
I have gotten this error as well. When I finally found the problem, the error wasn't in the snippets file for ADS at all. It was actually in the SSMS snippets file that it was trying to import fr...
I know this is a little late, but I had a similar, but not identical, problem quite a while ago. Mine was caused by a rogue character or two in the "description" of the snippet defined in SQL Prompt (for SSMS). I would check there to make sure you don't have any special characters there that might throw the parser for a loop. Once I changed the descriptions (I actually direct-edited the snippet file) of the offending snippets, the parser/imported worked just fine. / comments
I know this is a little late, but I had a similar, but not identical, problem quite a while ago. Mine was caused by a rogue character or two in the "description" of the snippet defined in SQL Prom...
I love the ability to customize the alert levels. This allows me to get pestered by emails from the issues that really matter (as defined by the team). That way there aren't too many alerts that consequently get ignored. / comments
I love the ability to customize the alert levels. This allows me to get pestered by emails from the issues that really matter (as defined by the team). That way there aren't too many alerts that ...
I have also noted how slow the performance is - since the beginning. I am using ver 0.2.5, now and it is no better. / comments
I have also noted how slow the performance is - since the beginning. I am using ver 0.2.5, now and it is no better.
@DanC Thanks for getting back to me and letting me know that a fix has been posted. I was able to download/install the new version. I can confirm that everything is looking much better on my end. The error does indeed appear to be resolved. / comments
@DanCThanks for getting back to me and letting me know that a fix has been posted. I was able to download/install the new version. I can confirm that everything is looking much better on my end. ...
When I go over to redgate.uservoice.com, there's no way to add a request/idea. SQL Monitor doesn't even show up in the list on the right hand side of the screen. [image] / comments
When I go over to redgate.uservoice.com, there's no way to add a request/idea. SQL Monitor doesn't even show up in the list on the right hand side of the screen.
I know I'm late to the party, but my two cents here: My team is now moving from TFVC to Git, because it's the defacto standard source control provider just about everywhere. We have SQL Source Control through the SQL Toolbelt. So we will be "trying" to develop database changes using Git and a Shared DB model. I agree with @LeeRobinson that the cost (in disk space (close to 2TB of data), effort, and time) to have dedicated development SQL Server environments setup locally precludes us from diving deep into that "distributed" model for DB development. @David Atkinson you mentioned the Flyway Desktop project. What's frustrating is that Flyway, if truly a rewrite of SQL Source Control, is now a separate cost. Selling that to my IT procurement team would be next to impossible. I love the Redgate tools, but me and my team are in the minority. So there's no path forward here to use Flyway. That means we are "stuck" using Git on SQL Source Control and developing in-house processes to make sure we don't do something stupid, or going back to TFVC for our database code. / comments
I know I'm late to the party, but my two cents here:My team is now moving from TFVC to Git, because it's the defacto standard source control provider just about everywhere. We have SQL Source Contr...
Thanks, for the tip on Octopus Deploy. However, since we are not licensed for SQLToolbelt Pro. We can't use the DLM Automation tool to integrate the two. Any other suggestions? / comments
Thanks, for the tip on Octopus Deploy. However, since we are not licensed for SQLToolbelt Pro. We can't use the DLM Automation tool to integrate the two. Any other suggestions?