Comments
Sort by recent activity
Thanks Brian I'll do that in the future. I still have one question however.
In an attempt to troubleshoot further I used a never version of my application which had the 7.0.0.772 version of the DLL in question. I did not have any issues and that version was compiled with the "any cpu" directive.
So what that just an issue with the 6.2.1 version? / comments
Thanks Brian I'll do that in the future. I still have one question however.
In an attempt to troubleshoot further I used a never version of my application which had the 7.0.0.772 version of the DL...
There are no brackets in the password.
From the help file, this is a sample that I was working from
master..sqlbackup '-SQL "BACKUP DATABASE pubs TO DISK = ''C:\Backups\pubs.sqb'' WITH PASSWORD = ''MyPassword'' " '
Alternatively, you can use square brackets instead of two single quotes:
master..sqlbackup '-SQL "BACKUP DATABASE pubs TO DISK = [C:\Backups\pubs.sqb] WITH PASSWORD = [MyPassword] " '
I did, however, do some further troubleshooting.
My actual password has an ascii 178(dec) or B2(hex) character in it which is a superscripted 2. This seems to be where the sqlbackup procedure is failing. When I create another backup without using this character, everything works in both the sql Command tool and the SqlBackup stored proc.
So it seems that the SqlBackup stored procedure has some difficulty with ascii characters above 122(DEC) or 7A(HEX) where the command line SqlBackupC command has no such issues.
It would be nice to see this limitation removed in a future release of SqlBackup.
BTW, I also got an exception in this post when I tried to use the actual character in the body of this message.
Thanks. / comments
There are no brackets in the password.
From the help file, this is a sample that I was working from
master..sqlbackup '-SQL "BACKUP DATABASE pubs TO DISK = ''C:\Backups\pubs.sqb'' WITH PASSWORD = ...
Thanks Brian
I think that this was actually due to the fact that our admin was making some network changes.
It was just concidence that I was able to delete my existing connections, close SBK, reopen SBK and readd my connections.
Thanks for the help / comments
Thanks Brian
I think that this was actually due to the fact that our admin was making some network changes.
It was just concidence that I was able to delete my existing connections, close SBK, reop...
I think I finally got this working. Looks like I just needed to be a little more proactive in monitoring the space that the log files are consuming.
It seems that simply backing up the transaction log and removing the inactive entries with SQL Backup does not shrink the log file very much. Some times the file shrinks a little, but the overall trend is that the file grows even though the actual data in the Log File is < 10% of the total file size. What I had to do was set up a daily job to monitor the size of the logs using DBCC sqlperf (logspace)
I have a server that hosts over 60 db instances. What happened in my particular instance was that once the transaction logs reach a certain size, SQL Backup stoped backing up the Transaction Logs because the time it thought it should take overlaped the next start. Once this happened, the transaction logs filled up and continued to grow.
The only way that I found to correct it was to stop all SQL Backup schedules and use dbcc shrinkfile and BACKUP LOG <DBName,SysName,dbName> WITH truncate_only on all my databases.
Once the database transaction logs were a manageable size again, I restarted SQL Backup Transaction Log backups. Now I monitor the log size daily. Once they reach a certain size I just have to use DBCC ShrinkFile to reclaim some of the empty space. / comments
I think I finally got this working. Looks like I just needed to be a little more proactive in monitoring the space that the log files are consuming.
It seems that simply backing up the transaction...
When you split the job into two can you just schedule one job, on it's own, to run successfully? If so what happens when you offset the second job, say by 15 mins? Does this then cause the jobs not to run?
When I split the job into two I can run one of the jobs.
Scheduling the 2nd job causes the "Conflicting Schedule" message to appear.
This happens no matter the offset. I tried offsetting for both 15 and 30 minutes.
It seems that once the "Conflicting Schedule" situation is detected that the job ceases to run.
Is SQL Backup a singleton class? If so, it does not matter how many schedules I create, it could never run more than one at a time. This would indicate to me that there is a fixed limit on the time SQL Backup Jobs can consume on any given Server.
Are there issues with running one or more Transaction Backups on different databases in parallel? It seems that this should effectively extend the amount of SQL Backup time that I have available per server. / comments
When you split the job into two can you just schedule one job, on it's own, to run successfully? If so what happens when you offset the second job, say by 15 mins? Does this then cause the jobs ...
Maybe you could put this one in a custom reporting FAQ.
I was able to find out where SQL Backup stores its backup history through forum posts. Thanks
Armed with this information, some simple queries and an xsl transform or two, I was able to create a backup reporting solution that fit my needs perfectly. / comments
Maybe you could put this one in a custom reporting FAQ.
I was able to find out where SQL Backup stores its backup history through forum posts. Thanks
Armed with this information, some simple querie...
Right, but to furthur your example, if I used check for update on SQL Backup, I would get, Product Up to date. I would have to keep checking all my products until I found one that had an update.
Since the update exe is already calling a webservice it would be nice if I could call that web service, just like the check for update exe is calling it. I would just need the wsdl or the soap structure that is expected so I could check all versions of my products at once. ie one click that would issue multiple webservice calls and display the information back to my app.
Thanks / comments
Right, but to furthur your example, if I used check for update on SQL Backup, I would get, Product Up to date. I would have to keep checking all my products until I found one that had an update.
S...
The CTRL+SHIFT+D hotkey answers my cache refresh
Thanks
But as for the schema panel, what you said is not always accurate.
Consider the following
I have the Aliases setting set to Enable Alias Assignment
I have tables
TableA
TableB
Here are examples of 'Ctrl + Space' sequences:
Select * From Tab[Ctrl + Space] -- This brings up the object definition dialog and the Schema Panel just fine.
However,
SELECT * FROM dbo.TableA[Ctrl + Space]
Produces
SELECT * FROM dbo.TableA ta -- no object definition dialog popup is ever displayed because intellisence has completed the statement
So if my object name can be determined by intellisence the object definition dialog never has a chance to popup.
I did, however, investigate a couple of other scenarios.
If I use this statment "SELECT * FROM dbo.TableA"
Put my cursor on the T and press [Ctrl + Space] then the object definition dialog comes up along with the Schema Panel.
So it is all about where your cursor resides when you press [Ctrl + Space] and if intellisence can determine your object name without the object definition dialog.
In any case, an explicit hot key for the schema panel would be nice.
Thanks, / comments
The CTRL+SHIFT+D hotkey answers my cache refresh
Thanks
But as for the schema panel, what you said is not always accurate.
Consider the following
I have the Aliases setting set to Enable Alias Assi...
I've only just begun to look at the new features, but so far its a big hit.
Thanks / comments
I've only just begun to look at the new features, but so far its a big hit.
Thanks