Activity overview
Latest activity by DWolford1234
DB Name with trailing space causes 6.4 to hang
Hello. I'm pretty sure this was a bug for the 5.x version of SQL Backup, and it was eventually resolved. However, I upgraded from 5.4 to 6.4 the other day, and my backups started to hang on one p...
BUG: Renamed Objects have original name in DDL Pane
I stumbled acrossed this earlier, was able to reproduce the issue, and thought I'd share.
I haven't tested if this is true with all object types, but it was reproducable with Stored Procedures.
Fir...
COPYTO Log Entries not shown in SQL Results
This may have been a problem forever, but I noticed today that the COPYTO messages that end up in the log files do not report in the SQL result set if the backup job is submitted as a T-SQL stateme...
Network Resiliency Testing Using MIRRORFILE
I'm not sure how widely this command is used, but I thought I'd give it a try and see if the network resiliency would work here as well.
FIRST-
I set up a network share as the destination of one of...
Good Lord!
16GB in 38seconds?!?
How do you live with yourself? [image] / comments
Good Lord!
16GB in 38seconds?!?
How do you live with yourself?
Yes, there are certainly many ways to work around the issue, and if I had such a tight backup window as I described above, I would probably create a seperate job as well. One would just do local backups, and the other would do the copy. However, in the context of providing feedback for the network resiliency feature, it'd be nice to see a queuing option and be able to have the solution all bundled up. / comments
Yes, there are certainly many ways to work around the issue, and if I had such a tight backup window as I described above, I would probably create a seperate job as well. One would just do local b...
Glad to hear it. Also glad to know it wasn't just me! [image] Seems like I'm the only one who was seeing this issue. / comments
Glad to hear it. Also glad to know it wasn't just me! Seems like I'm the only one who was seeing this issue.
Network Resilience Comment
I don't think this is the constructive feedback you are looking for, but it is a comment.
I like the resiliency, but I wish it had been built to queue up the failed network copy operation until aft...
Cool. I've saved the profile history for those three servers. If you end up needing the history to see the order of events that the GUI is doing, let me know, and I'll e-mail it. / comments
Cool. I've saved the profile history for those three servers. If you end up needing the history to see the order of events that the GUI is doing, let me know, and I'll e-mail it.
There's nothing in the log files except these two lines:
12:57:29.740|Info |UI |1 |SQL Backup Client 6.0.0.339
12:57:29.755|Info |UI |1 |=======================================
However.... I went ahead and set up profiler on several SQL servers waiting for the the error to show up and then seeing what the final command was. I found a commonality, and can reproduce the error when I run the following command in query analyzer / managment studio.
master..sqbdata 'SELECT COUNT(*) FROM backuphistory WHERE id > 0 AND backup_start < ''0001-01-06 00:00:00'' AND backup_end > ''0001-01-01 00:00:00'' '
This same command was sent to three different servers at just about the same time... All of them then had the error. For some reason the year is being sent as 0001.
Even if the year were correct, I would expect you to always get a count of 0 with that logic.
From what I can see in the profile history..nowhere else is that command sent before this occurrence with or without valid year.
Hopefully, this info will let you find it in the code.
Good luck,
Dan W / comments
There's nothing in the log files except these two lines:
12:57:29.740|Info |UI |1 |SQL Backup Client 6.0.0.339
12:57:29.755|Info |UI |1 |====================...