Comments
Sort by recent activity
Fair enough. It was actually after 1 AM when I was on, apparently I selected the wrong time zone change and I am just to lazy to change it. You are quite right about 'oops' decisions being made late into the night.
BTW it worked correctly this time. It is amazing what happens when all the pieces are in place.
8) / comments
Fair enough. It was actually after 1 AM when I was on, apparently I selected the wrong time zone change and I am just to lazy to change it. You are quite right about 'oops' decisions being made l...
Relax, I am not looking for someone else to blame if it goes sideways. I can do the research on the correct syntax.
I appreciate the help. / comments
Relax, I am not looking for someone else to blame if it goes sideways. I can do the research on the correct syntax.
I appreciate the help.
Ok, so let me get this straight, you're saying that I cannot create the converted file because I the system I am using is FAT32 instead of NTFS? Of course you are. So, you wouldn't happen to know of an easy, painless way to convert from FAT32 to NTFS. If memory serves, you can convert from NTFS to FAT32, but not the other way around. Please tell me I am wrong. / comments
Ok, so let me get this straight, you're saying that I cannot create the converted file because I the system I am using is FAT32 instead of NTFS? Of course you are. So, you wouldn't happen to know...
Nope, FAT32. / comments
Nope, FAT32.
No problem. First, no errors reported, all backups were successful. Second, RESTORE SQBHEADERONLY is not a recognized command and I am running it on the server that has SQL Backup installed on it. Of course that is through the Query Analyzer not via the command prompt. Here is what you're looking for:
Backup group ID: 49733565
File Number: 1 of 1
Backup Size: 8.320 GB
Backup start: today @ 0840
Backup end: today @ 0844
Server Name:
Instance: (local)
Database name: herbert
First LSN: 466375000007993100001
Last LSN: 466375000007993300001
Checkpoint LSN: 466375000007993100003
Differential base LSN: 466375000007988400002 / comments
No problem. First, no errors reported, all backups were successful. Second, RESTORE SQBHEADERONLY is not a recognized command and I am running it on the server that has SQL Backup installed on it...
OK, here are the results. The BackupName is marked as *** INCOMPLETE ***, Position is 1 and the rest is NULL. / comments
OK, here are the results. The BackupName is marked as *** INCOMPLETE ***, Position is 1 and the rest is NULL.
Here is some additional information. I tried running the convert again and for the new version 3.2.0 there is a progress echo, it got to 40% then stopped and reported that the MTF file created. Strangely enough it would appear that the percentage reported as being converted is about the percentage that is restored prior to failing. / comments
Here is some additional information. I tried running the convert again and for the new version 3.2.0 there is a progress echo, it got to 40% then stopped and reported that the MTF file created. S...
I will have to run it tomorrow morning when I get to the office. I will post the results. Unfortunately I cannot send the file for two reasons, the compressed file is 1.4 GB and it is confidential. / comments
I will have to run it tomorrow morning when I get to the office. I will post the results. Unfortunately I cannot send the file for two reasons, the compressed file is 1.4 GB and it is confidential.
There are limitations, SQL Backup will only handle passwords that are less than 17 characters in length. I have not found any characters that are restricted, but like I said earlier, nothing that fancy just basic keyboard characters used.
What is the possibility that a future release will allow for longer passwords to be used? / comments
There are limitations, SQL Backup will only handle passwords that are less than 17 characters in length. I have not found any characters that are restricted, but like I said earlier, nothing that ...
Got it. Thanks. / comments
Got it. Thanks.