Comments
Sort by recent activity
Brian,
Problem #2 shows that I am trying to take the latest good backup and restore it via SQL Backup. The server seems to be restarting whenever the system issues a WITH RECOVERY statement after the last transaction log has been restored.
This still doesn't cover the issue of Problem #1, which is essential when trying to recover everything possible after your database has been marked suspect, which is making a backup of the transaction log with no_truncate.
This also doesn't cover the issue of Problem #3, which points out a bug in the SQB to MTF conversion software, decompressing from level 1 to native SQL backup files.
Laurence / comments
Brian,
Problem #2 shows that I am trying to take the latest good backup and restore it via SQL Backup. The server seems to be restarting whenever the system issues a WITH RECOVERY statement after ...
Thank you Nick. Just for clarity, I wasn't trying to find a replacement for our source control. I was trying to find a way to display it via a web interface so that my boss or anyone else who is interested doesn't have to have the source control software installed. I figured this would be able to do that.
Laurence / comments
Thank you Nick. Just for clarity, I wasn't trying to find a replacement for our source control. I was trying to find a way to display it via a web interface so that my boss or anyone else who is ...
1. When I launch the application, it automatically defaults to local as the name of the SQL Server located on my workstation. The name is greyed out and doesn't allow me to change it to the actual name of the instance, which would be TXXPW204 in this case.
2. Your data sheet on SQL Doc says the following:
"When should I use SQL Doc?
SQL Doc is a simple tool designed to document and export database schemas into HTML for many different tasks: a history of changes, QA purposes, dependency analysis and reporting."
I'm not looking for it to replace my current source control. I'm looking for a way to display what I currently have within my source control. Per the PDF data sheet, we should be able to do that.
Laurence / comments
1. When I launch the application, it automatically defaults to local as the name of the SQL Server located on my workstation. The name is greyed out and doesn't allow me to change it to the actua...
It's because the previous DBA set up a job that runs on a nightly basis and adds an email notification step to each job that doesn't have it. Some servers that were created or modified after his departure don't have this job running on it, which explains why I can modify them with the GUI and not the others.
Laurence / comments
It's because the previous DBA set up a job that runs on a nightly basis and adds an email notification step to each job that doesn't have it. Some servers that were created or modified after his d...
Son of a gun. Thanks cgriffin. I think I know why we're having our issues on certain servers and not on others.
Laurence / comments
Son of a gun. Thanks cgriffin. I think I know why we're having our issues on certain servers and not on others.
Laurence
I agree with cgriffin. I think we need to have the ability to edit the jobs created by SQL Backup. It provides a simple interface that we can create a simple manual off of for when we are on vacation and someone with less experience needs to access the jobs. I love the new GUI, but it does have its shortcomings, such as being able to edit a job after you create it and reboot your workstation. Also, we can install the server components remotely but we can't remove them remotely. Is there a place we can make suggestions?
Laurence / comments
I agree with cgriffin. I think we need to have the ability to edit the jobs created by SQL Backup. It provides a simple interface that we can create a simple manual off of for when we are on vaca...
I'm back and I'm still convinced this is a bug and not a security feature. We should be able to edit all jobs all the time through the GUI on a remote master workstation/server because of the following scenarios:
1. I have 13 production servers, 3 of which I am able to edit, 10 of which I am not able to edit.
2. I don't see a difference between servers on the surface that jump out at me pointing to the reason why I can edit Server 1 and not Server 2.
3. This only occurs after you restart the workstation/server the GUI resides on.
4. I have another co-worker at an site in Europe that ran into the same issues of being able to create a job, tinker with it all day long, and unable to mess with it the next day.
It would be different story if I wasn't able to edit any server, then I would say it could fall under the security feature aspect. But that's not the case. Can someone please look into this? It has to do with the remote aspect of it because you can edit all day long if the GUI is directly on the SQL Server in question, so it's not a GUI issue.
Thanks,
Laurence / comments
I'm back and I'm still convinced this is a bug and not a security feature. We should be able to edit all jobs all the time through the GUI on a remote master workstation/server because of the foll...
I'm not sure if the administrators will allow me to do that since I am using Remote Desktop to connect in and install the software. I did figure out a work around though, which was using the GUI console on my workstation to remotely install the software on the SQL Server. It doesn't provide the server with the software to manage it directly on the server, but it does provide what I need to backup the databases.
Laurence / comments
I'm not sure if the administrators will allow me to do that since I am using Remote Desktop to connect in and install the software. I did figure out a work around though, which was using the GUI c...
Petey,
We are using SQL Server 2000 Standard Edition with SP4 on Windows Server 2003 with SP2. We are not using SQL Server Compact Edition. I did not receive any warning or error message during the test backup. / comments
Petey,
We are using SQL Server 2000 Standard Edition with SP4 on Windows Server 2003 with SP2. We are not using SQL Server Compact Edition. I did not receive any warning or error message during t...
I was able to successfully create a SQL Backup of the model database with the command given. Why am I not able to connect via the GUI console so I can activate the license and manage it?
Laurence / comments
I was able to successfully create a SQL Backup of the model database with the command given. Why am I not able to connect via the GUI console so I can activate the license and manage it?
Laurence