Comments
Sort by recent activity
Eddie -
In preparing to take the actions you suggested, I went onto the two servers that were giving my PC GUI of SQL Backup 'fits'. But, this time, both SQL Backup GUIs on the servers showed the same update icon that was being displayed on the PC; what is strange is that they were not when I first reported this problem.
I have clicked the upgrade button on each server's GUI and the problem is resolved.
As to why it took so long for the server's GUI to show the upgrade available button ... I have no idea, but wanted to pass this on to you and close this out.
Regards
Randy Volters / comments
Eddie -
In preparing to take the actions you suggested, I went onto the two servers that were giving my PC GUI of SQL Backup 'fits'. But, this time, both SQL Backup GUIs on the servers showed the ...
Incident type: Job did not start
Subject: <Job name is here>
Incident Time: 2/28/2008 8:05:00 AM
SQL Server <server name is here>
Job name: <Job name is here>
Description: <description of job is here>
Category: [Uncategorized (Local)]
Owner: <owner name is here>
Run <batch name is here>
Step name: <step name is here>
Subsystem: TSQL
Run Status: Succeeded
Command: <sproc name is here>
Additional Information:
Executed as user: <user name is here> The step succeeded.
DateTime is correct.
Kind of peculiar, it knows the job succeeded, but reports that it didn't start.
(Beta anyway, but this is the point of posting the confirmation, hope this helps in some way.) / comments
Incident type: Job did not start
Subject: <Job name is here>
Incident Time: 2/28/2008 8:05:00 AM
SQL Server <server name is here>
Job name: <Job name is here>
Description: <description of job is he...
Thanks.
This makes sense; but our installation of SQL Backup rests directly on the SQL Server. The only people that are allowed login access to the server already have file browsing ability through explorer - so the risk is nill for our installation.
Otherwise, I'd leave it the way it is configured.
Thanks for the info. / comments
Thanks.
This makes sense; but our installation of SQL Backup rests directly on the SQL Server. The only people that are allowed login access to the server already have file browsing ability throug...
Yes, I know about shift & cntrl+shift.
These are ok, but nothing beats a quick cntrl+a [image] / comments
Yes, I know about shift & cntrl+shift.
These are ok, but nothing beats a quick cntrl+a
Hello Jason -
Well, I don't know if this is possible, but what would be useful is:
Machine Total Memory Available NN GB
Memory Allocated to SQL Srvr NN GB YY % of Total memory
Memory Currently Used NN GB YY % of Memory Alloc.
Memory Available NN GB YY % of Memory Alloc.
It would also be helpful if, in the final product a threshold is 'settable' by the end user over which the alert would be made manifest (such as show me when consumed memory reaches NN GB and/or YY %). Even better would be a couple of thresholds; warning (yellow) and critical (red).
(As long as you're asking ;-) / comments
Hello Jason -
Well, I don't know if this is possible, but what would be useful is:
Machine Total Memory Available NN GB
Memory Allocated to SQL Srvr NN GB YY % of T...
James -
That worked.
thanks much / comments
James -
That worked.
thanks much
James -
I think you hit the nail on the head. Unfortunately, they are training late tonight, and appear to be using the database so I'll have to wait to confirm. But I did get through the operation, it just failed because the database is in use.
I'll post a success story after I get everyone off and have successfully restored.
Thanks. / comments
James -
I think you hit the nail on the head. Unfortunately, they are training late tonight, and appear to be using the database so I'll have to wait to confirm. But I did get through the operati...
The reports are quite handy as well.
I had a little problem figuring out the new UI for restoring a file, but James helped me out and I had it restored in no time.
I cannot find anything about this release that I do not like.
Very, very content.
Of all the tools, this one is the one I use the most, like the best.
Now, if we could only get log rescue for SQL Server 2K5... [image] / comments
The reports are quite handy as well.
I had a little problem figuring out the new UI for restoring a file, but James helped me out and I had it restored in no time.
I cannot find anything about this...
I use DOMAIN\ACCOUNTNAME / comments
I use DOMAIN\ACCOUNTNAME
Are you (the installer) a local admin, domain admin or standard user - is it a domain account or a local account?
> I am the DOMAIN Administrator, as well as the LOCAL Administrator.
Similarly for the SQL Backup Agent user, SQL Server user and SQL Agent User?
> The service account is a member of both LOCAL and DOMAIN Administrators. Additionally, because we config'd SQL Server to use AWE, there is a group policy entry that permits this account to Lock Pages in Memory. (I posted about this in SQL Backup 4).
Are the accounts above the same account (installer, backup agent ...) or different accounts?
> Different. I, as Administrator, installed the product. The account that runs SQL Backup is a an account that was assigned to run as the service account for SQL Agent.
Are SQL Server and SQL Backup running as the same account?
> Almost correct - SQL Server, SQL Agent & SQL Backup are running under the same service account.
Do you have multiple instances per machine?
> NO, single instance.
Are you running SQL 2000, SQL 2005 or both?
> SQL Server 2005. / comments
Are you (the installer) a local admin, domain admin or standard user - is it a domain account or a local account?
> I am the DOMAIN Administrator, as well as the LOCAL Administrator.
Similarly for ...