Now it's time to see how this really works. How does this sound? Pretty good to me, so I took the next step after a few days of letting this run on my test system. I suspect they are capturing only the time to grab the data pages and write them out, rather than the entire stored procedure time. This same operation, according to my maintenance plan logs, took 1:38, so this database went from 405MB to 105MB and was quicker with Litespeed! The vendor has acknowledged some discrepancies with the times reported. One thing I noticed with further testing, in QA, the query for the backup took 1:12 to run, though the time is shown as 28 seconds. Processed 1274 pages for database 'epo', file 'ePO_log' on file 1.īACKUP DATABASE successfully processed 53202 pages in 28.412 seconds (15.339 MB/sec). Processed 51928 pages for database 'epo', file 'ePO' on file 1. Here are the results: MethodĪfter the backup is complete, the stored procedure reports data like so: The first test was to perform a backup of 25MB db. I am currently using a maintenance plan, so I have some statistics, but I decided to run Profiler and Performance Monitor and gather more information. Instead, there are a few simple extended stored procedures that you use to take advantage of this product.įirst step, benchmark a backup of my databases for full backups Once installed, there is no program to run. Less than a minute once I located the license key. Product installed flawlessly and quickly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |