Comments
Sort by recent activity
I too have noticed the same thing. I will run some backup in QA. The informational message will say the backup took 1-2 seconds, but the query actually took 30 or so seconds. Here's an actual example:
1. EXEC master..sqlbackup '-SQL "BACKUP DATABASE CME_TRAIN_GLL TO DISK = ''C:\BACKUPS\DB\<AUTO>'' WITH ERASEFILES=2,COMPRESSION=1, VERIFY" -E"'
the output from this command says: BACKUP DATABASE successfully processed 21009 pages in 2.490 seconds (69.115 MB/sec). But in QA it actually took 10 seconds to execute.
2. backup database CME_TRAIN_GLL to DISK='c:\BACKUPS\DB\CME_TRAIN_GLL_FULL_20050609.BAK' with init
The output from this command says BACKUP DATABASE successfully processed 21009 pages in 5.664 seconds. (30.384 MB/sec) QA says it actually took 6 seconds to execute which is about right.
The SQL Backup version is smaller but it doesn't seem to execute in less time despite what it says. / comments
I too have noticed the same thing. I will run some backup in QA. The informational message will say the backup took 1-2 seconds, but the query actually took 30 or so seconds. Here's an actual e...
We use SQL compare to promote changes to objects from Dev, to stage, to Prod. This helps ensure consistency in the various environments. We have on more than one occasion found objects that someone "forgot" in stage and never promoted up. It is a valuable tool in our change process. / comments
We use SQL compare to promote changes to objects from Dev, to stage, to Prod. This helps ensure consistency in the various environments. We have on more than one occasion found objects that someo...
Check why there is lots of space. Are there particular tables with indexes that are very large having lots of unused space. If so you can try to reorg indexes of ever drop unused indexes to free up space. There are lots of scripts available that will help you find space used by table as well as space used by indexes. Look at some of your larger tables first but look at tables that have indexes with large amounts of unused space as well. / comments
Check why there is lots of space. Are there particular tables with indexes that are very large having lots of unused space. If so you can try to reorg indexes of ever drop unused indexes to free ...
If this is still an issue, check where is the bloat. Often indexes contribute to this. You can try reorging or rebuilding indexes to see if this helps. Reorging an index is process that can be stopped and restarted later. Reindexing rolls back so this is different but at least this process can be done bit by bit. Stat with finding some of your large tables and checking out the index sizes. / comments
If this is still an issue, check where is the bloat. Often indexes contribute to this. You can try reorging or rebuilding indexes to see if this helps. Reorging an index is process that can be s...
Thanks. I tried it again and it works as expected / comments
Thanks. I tried it again and it works as expected
When I run C:\Program Files\Red Gate\SQL Backup\SQBServerSetup.exe I enter in all information including userid/password of cluster id I get an error that read: Internal error'RunTime Error' at 117:829 Generic failure. / comments
When I run C:\Program Files\Red Gate\SQL Backup\SQBServerSetup.exe I enter in all information including userid/password of cluster id I get an error that read: Internal error'RunTime Error' at ...
I get the same error but my database has a recovery model of full / comments
I get the same error but my database has a recovery model of full