The One SQL Tool That Might Save Your Job

What happens when you load up Query Analyzer, generate a database script based off an existing database, then run that script to create an identical database? Theoretically, it creates the new database, right? Well... some times, query analyzer decides to put “USE“ statements inside the script, which means that instead of creating the new database, you will drop all the tables in the old database and then recreate them... which, of course, means that all your data will instantly dissappear (doesn't matter if it is $10 of data, or $10 million dollars of data, it will be gone). Now, assuming that your backups are all running (and are in working order), and your transaction logs contain all the information you need (which won't be the case if you are using image or text fields and haven't set explicitly told SQL to save that info), you might be able to undo the damage. But, you know what they say about assumptions...

So, if your assumption turns out to be incorrect, go get a copy of Lumigent's SQL Log Explorer. Not only is it a niftly little tool, but if you catch your error quickly and make a copy of the DB before too much new data is inserted, it can also magically restore data from dropped tables (no backups required).

7 Comments

  • This tool has saved me on two occasions!

  • great shill but at if I spent $10,000 plus more for mandatory support for Lumigent's product I'd LOSE my job - not get it saved.

  • the problem i am seeing with these kinds of BLOGs is that they are often worse than no information at all. If you are going to post something - at least provide some thought and effort to consider alternative products. 2 have been mentioned here by other posters. Mention the downsides - not just school girl gushing praise ("magically"). We looked at Lumigent and it was going to cost more than we paid for SQL Server itself!



    we see enough propaganda from vendors without BLOGs parroting their "talking points" and serving as just free advertising.

  • You cheap bastard. Anyone who works with any projects of any importance realizes that your data is worth far more than the price of SQL server. The issue is not that Lumigent's tool is expensive as much as it is that SQL server is so cheap. Go get a real job and stop whining.

  • so let me get this straight - YOU were too cheap to buy Oracle in the first place (which has integral transaction log reading support) but anybody who doesn't want to pay more for this particular add-on than the base price of sql server itself is a "cheap bastard". You say the issue is that "sql server is so cheap" so I guess since you are using it by definition you must be too. But keep paying thousands for add-ons and you will prove us wrong. I would love to see your final cost when you have achieved the functionality that Oracle delivers out of the box!



    keep up the good work genious

  • Personally, I would use SQL Server over Oracle any day, and it has nothing to do with price. Price and value are two very different things, a point which you obviously are missing.



    In any case, SQL Server does fully support transaction logs; however, if you have (a) cleared the transaction log manually or (b) are using Image or Text columns and have not specified that they need to be included in the transaction log, and then you drop a table, restoration goes far beyond what transaction logs of any system will do (including the rip off product that Oracle offers). What is great about Lumigent's tool is that it doesn't need transaction logs to operate (otherwise, I agree that it would be quite useless). If the space inside the DB hasn't been overwritten by new data, it can actually read the raw file from disk and reconstruct the tables for you manually.

  • "SQL Server does fully support transaction logs" - is this why Microsoft Encrypts the Log output thus forcing you to buy an expensive 3rd party add-on just to read it? Great value!





Comments have been disabled for this content.