How can we help you today? How can we help you today?
zynrg
Activity overview Badges (0) Posts (4) Comments (8)

Comments

Sort by recent activity
I see. That means each time when SQL Data Compare 7 gets involved in backup comparison, it actually extracts all the content of backups and then compares them. If so, it's absolutely convenient for small databases, but for big databases, I'd rather restore them first and then compare them because it takes the same time and is more flexible. Are there any means that we can just grab part of backups and get it fast? [image] / comments
  1. Community
  2. SQL Data Compare Previous Versions
  3. Doesn't work when comparing TB live DB with its backup file
I see. That means each time when SQL Data Compare 7 gets involved in backup comparison, it actually extracts all the content of backups and then compares them. If so, it's absolutely convenient for...
0 votes
Hi Petey, You are right. I will catch the exit code 580 and deal with it specificly. Thanks, [image] Neo / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Cannot catch the error when the backup file is in use
Hi Petey, You are right. I will catch the exit code 580 and deal with it specificly. Thanks, Neo
0 votes
Hi Petey, Thanks for your quick answer. I can catch the exit code, but the exit code is 500 (General SQL Backup error). It doesn't indicate anything. Generally, I use a variable table to catch errors, such as Insert into @ErrorTable EXEC master..sqlbackup '-sql "..."', @exitcode OUTPUT, @sqlerrorcode OUTPUT It works perfectly; however, it doesn't return a dataset only when the backup file is used by another process. Is there any way I can catch the error message? Neo / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Cannot catch the error when the backup file is in use
Hi Petey, Thanks for your quick answer. I can catch the exit code, but the exit code is 500 (General SQL Backup error). It doesn't indicate anything. Generally, I use a variable table to catch erro...
0 votes
Hey Petey, That's exactly what I want, "WITH SINGLERESULTSET". Thank you a lot for your quick reponses. BTW, probably, I'm the first one who want to use this funcationality in programming. [image] It's easy for human beings to read but hard for machines, even I use "WITH SINGLERESULTSET", it still need some further process to deal with the info. Anyway, it will be great, if you could add a parameter to let people specify the result format. That's only my personal suggestion. [image] Thanks again. Neo / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Got an error when trying to use "Restore headeronly"
Hey Petey, That's exactly what I want, "WITH SINGLERESULTSET". Thank you a lot for your quick reponses. BTW, probably, I'm the first one who want to use this funcationality in programming. It's ea...
0 votes
Yes, exactly, but it's entirely different from the sqlserver's result format. If you use FILELISTONLY, you can get the same result as sqlserver's. Actually, I'm using "Insert into @TempTable Exec(@Sql)", but if the result returns two tables with different column amount, I could not get the info. So far, I cannot figure out how to get these info in my stored procedure. Why you design it like this? Or give me some suggestions. Thanks, / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Got an error when trying to use "Restore headeronly"
Yes, exactly, but it's entirely different from the sqlserver's result format. If you use FILELISTONLY, you can get the same result as sqlserver's. Actually, I'm using "Insert into @TempTable Exec(@...
0 votes
Hey Petey, You may download this file and try it. http://pickup.mofile.com/6330744401386462 declare @sql varchar(max) set @sql = '-SQL "Restore headeronly from disk = ''E:\Backup_A\FULL_(local)_model_20071203_234217.sqb''"' exec master.dbo.sqlbackup @... [/url] / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Got an error when trying to use "Restore headeronly"
Hey Petey, You may download this file and try it.http://pickup.mofile.com/6330744401386462 declare @sql varchar(max) set @sql = '-SQL "Restore headeronly from disk = ''E:\Backup_A\FULL_(local)_mode...
0 votes
Thanks Petey for your reply. I don't think it's a file-related issue because I have tried a couple of files. RESTORE FILELISTONLY works, but RESTORE VERIFYONLY and RESTORE SQBHEADERONLY don't work as well as HEADERONLY. BTW, currently, I'm using 5.2 version for SQL 2005. Here are some results: --===============================================================-- declare @sql varchar(max) set @sql = '-SQL "Restore verifyonly from disk = ''E:\Backup_A\FULL_(local)_master_20071203_234212.sqb''"' exec master.dbo.sqlbackup @... SQL Backup v5.2.0.2807 Verifying file: E:\Backup_A\FULL_(local)_master_20071203_234212.sqb Attempting to restore this backup may encounter storage space problems. Subsequent messages will provide details. Directory lookup for the file "D:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf" failed with the operating system error 3(The system cannot find the path specified.). Directory lookup for the file "D:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf" failed with the operating system error 3(The system cannot find the path specified.). The backup set on file 1 is valid. SQL Backup process ended. (10 row(s) affected) name value exitcode 0 sqlerrorcode 0 filename001 E:\Backup_A\FULL_(local)_master_20071203_234212.sqb (3 row(s) affected) --===============================================================-- --===============================================================-- declare @sql varchar(max) set @sql = '-SQL "Restore headeronly from disk = ''E:\Backup_A\FULL_(local)_master_20071203_234212.sqb''"' exec master.dbo.sqlbackup @... SQL Backup v5.2.0.2807 Reading file header of "E:\Backup_A\FULL_(local)_master_20071203_234212.sqb" Backup name : Database (master), 12/3/2007 11:42:12 PM Description : Backup on 12/3/2007 11:42:12 PM Server: CTESDTSS Database: master Backup type : 1 (Database) User name : CTESDTSS\osun Backup start : 12/3/2007 11:42:13 PM Backup finish: 12/3/2007 11:42:13 PM Server name : CTESDTSS Database name : master Database version : 611 Creation date : 11/14/2007 6:24:11 PM Size : 3.313 MB Sort order : 52 Code page : 0 Machine name : CTESDTSS Collation : SQL_Latin1_General_CP1_CI_AS First LSN : 432000000003200037 Last LSN : 432000000005600001 Checkpoint LSN : 432000000003200037 Database backup LSN : 431000000019200037 Differential base LSN : NULL SQL Backup process ended. (28 row(s) affected) name value exitcode 0 sqlerrorcode 0 filename001 E:\Backup_A\FULL_(local)_master_20071203_234212.sqb (3 row(s) affected) --===============================================================-- --===============================================================-- declare @sql varchar(max) set @sql = '-SQL "Restore sqbheaderonly from disk = ''E:\Backup_A\FULL_(local)_master_20071203_234212.sqb''"' exec master.dbo.sqlbackup @... SQL Backup v5.2.0.2807 Reading SQB file header of "E:\Backup_A\FULL_(local)_master_20071203_234212.sqb" Backup group ID : 100457965 File number : 1 of 1 Backup type : 1 (Database) Native backup size : 3.688 MB Database size : 5.000 MB Backup start : Monday, December 03, 2007 11:42:13 PM Backup end : Monday, December 03, 2007 11:42:13 PM Server name : CTESDTSS Database name : master First LSN : 432000000003200037 Last LSN : 432000000005600001 Checkpoint LSN : 432000000003200037 Database backup LSN : 431000000019200037 (20 row(s) affected) name value exitcode 0 sqlerrorcode 0 filename001 E:\Backup_A\FULL_(local)_master_20071203_234212.sqb (3 row(s) affected) --===============================================================-- / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Got an error when trying to use "Restore headeronly"
Thanks Petey for your reply. I don't think it's a file-related issue because I have tried a couple of files. RESTORE FILELISTONLY works, but RESTORE VERIFYONLY and RESTORE SQBHEADERONLY don't work ...
0 votes
Hey Petey, Here is the resutl: 12/5/2007 11:32:22 AM Not encrypted 12/5/2007 11:32:22 AM Single device file 12/5/2007 11:32:22 AM Compression level: 1 12/5/2007 11:32:22 AM File size: 664,576 12/5/2007 11:32:23 AM File read stopped at position: 664,233 12/5/2007 11:32:23 AM Remaining: 343 12/5/2007 11:32:23 AM Validating remaining bytes... 12/5/2007 11:32:23 AM File appears to be valid 12/5/2007 11:32:23 AM File read ended at position: 664,576 Did you try HEADERONLY on your computers? Could you successfully run it? Thanks, / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Got an error when trying to use "Restore headeronly"
Hey Petey, Here is the resutl: 12/5/2007 11:32:22 AM Not encrypted 12/5/2007 11:32:22 AM Single device file 12/5/2007 11:32:22 AM Compression level: 1 12/5/2007 11:32:22 AM File size: 664,5...
0 votes
Total activity
15
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
3