Have you ever found yourself living David Byrne’s dire prophecy? (http://www.youtube.com/watch?v=I1wg1DNHbNU... Don’t try to reenact… the 80’s were more tolerant to bizarre body movements, tics and twitches advertised as a ‘dance’)
Specifically, when you develop SQL, has it ever happened to you that you’ve casually run some UPDATE or DELETE statement, and got the message that… say, way more records than you had intended were just deleted? And you sit there, staring at the screen, letting the fact of what just happened enter your mind little by little… and the only thought in your mind is… “holy sh**!”
Hopefully you’ve got backup. And a pretty recent one too. And the time to go through the restore hassle.
SQL doesn’t have an ‘undo’. That bothered us for years. We have partially answered this problem with our Data Profiler, which enables you to take quick snapshots of the data before you’re changing anything. But that’s not a full solution.
We’ve now taken a further step in that direction: Our new Colombo can take a DML statement (INSERT, UPDATE or DELETE) detect exactly what changes its going to make, and generate the SQL script that will do the exact opposite of what the statement does. NICE. Well, we think so. You simply paste your statement into Colombo, select your database, and that’s it!
There is still considerable way to walk to provide a full undo to every sql operation, batch script, and stored procedure that you might call. And we intend to walk that road. For now, we’ve taken the first step. Think we’re crazy? Let us know…
(Now that song will be stuck in my head for the next 3 days. It’s the same problem with anything 80’s….)