Drew Furgiuele is building a bridge to nowhere in SQL Operations Studio:
So when I sat down to write noWHERE, the concept seemed simple enough: I’ll code some text parsing into extension.js to look at the editor window’s text and look for UPDATE and DELETE statements and then try to see if there’s a missing WHERE clause. Seems reasonable enough, right? Except writing a SQL parser isn’t really something I want to do (or would be ABLE to do, frankly).
Since the module is written in JavaScript, I can leverage node.js modules to do most of the work for me. In this case, I downloaded a module called sqlite-parser. It’s a barebones, no-frills SQL syntax parser. It doesn’t support any dialect-specific stuff for T-SQL, but for this initial project, I only really care about ANSI UPDATE and DELETE statements.
There’s also a T-SQL parser available via Powershell, though I suppose that one isn’t directly available within SqlOps. One thing that would make this really good would be to intercept the execute operation and pop up a warning dialog if there’s no WHERE clause. There are some third-party tools which do this for Management Studio and a gate like that really saves you in the event of an emergency.