Comments
Sort by recent activity
Hi,
It's as simple as it sounds - just uninstall it from your 'incorrect' machine and install it on the correct one. You should be able to activate the software with no problems if this is done, however if you do receive an error when you attempt to activate the software, please email us on 'support AT red-gate.com', and we will sort it out for you.
Simon / comments
Hi,
It's as simple as it sounds - just uninstall it from your 'incorrect' machine and install it on the correct one. You should be able to activate the software with no problems if this is done, h...
Hi Mark,
Sorry it has taken so long to get back to you. We have logged a support call for you regarding this issue, and will email you shortly with how to move your copy of SQL Bundle.
Regards
Simon / comments
Hi Mark,
Sorry it has taken so long to get back to you. We have logged a support call for you regarding this issue, and will email you shortly with how to move your copy of SQL Bundle.
Regards
Simon
Hi,
If you need to run backups using SQL Backup from the passive node of your cluster, you will need a license for each node as they are both physical servers which require the extended stored procedures to be installed. Therefore for your cluster you will need two licenses.
However if you never need to run backups from your passive node (ie you never would use the passive node unless there was an emergency), and hence you do not install the SQL Backup extended stored procedures on the passive node, you will only need one license.
I hope that this answers your question. / comments
Hi,
If you need to run backups using SQL Backup from the passive node of your cluster, you will need a license for each node as they are both physical servers which require the extended stored proc...
Hello,
The way the licensing works is that to back up a SQL server, you need to install the SQL Backup extended stored procedures on that SQL server. And for every server the extended stored procedures are installed on, a license is required.
So basically if you are backing up a server with SQL Backup, you require a license for it. However if you have the Pro version of SQL Backup and are administering the backups on remote SQL servers from a workstation, you do not need a license for your workstation.
I hope this helps - if you have any more questions, please ask. / comments
Hello,
The way the licensing works is that to back up a SQL server, you need to install the SQL Backup extended stored procedures on that SQL server. And for every server the extended stored proce...
Hi Joe,
If you mean that you have damaged one of your databases, and are wondering if you can recover it by using the update script from Data Compare, then no unfortunately this is not possible.
If you are asking for another reason, please let us know.
Regards
Simon / comments
Hi Joe,
If you mean that you have damaged one of your databases, and are wondering if you can recover it by using the update script from Data Compare, then no unfortunately this is not possible.
If...
Hello,
Sorry to hear this - have you received any of these recently? There was an internal systems issue on the server which generates these reports, but this has now been resolved.
If you're still not receiving them, let us know. / comments
Hello,
Sorry to hear this - have you received any of these recently? There was an internal systems issue on the server which generates these reports, but this has now been resolved.
If you're stil...
Apologies for the delay - your username has been changed. You'll need to use the new one to log in from now on. / comments
Apologies for the delay - your username has been changed. You'll need to use the new one to log in from now on.
We can change it for you.
What would you like it changed to? / comments
We can change it for you.
What would you like it changed to?
Did you change the default installation location when you installed SQL Monitor? If so, the file might be in a different location.
For example, on my production installation of SQL Monitor, it is in [image] \ProgramData\Red Gate\SQL Monitor 2.
Simon / comments
Did you change the default installation location when you installed SQL Monitor? If so, the file might be in a different location.
For example, on my production installation of SQL Monitor, it is ...
Hello,
Can I just clarify what you would like to do? Are you talking about moving the installation of the SQL Monitor web front end into your DMZ, installing a second web front end in the DMZ, or something else entirely?
How we did this at Red Gate was to leave the SQL Monitor web site/front end on the internal network, and then publish it externally using an ISA 2007 server which we already had in production in our DMZ for providing Exchange OWA externally. Doing it this way meant that even though we weren't using IIS as the web server on the SQL Monitor box (it was installed with the self contained web server), we could still configure SSL for external connections. Obviously this is only a useful solution if you already have an ISA/Forefront type server, or are prepared to install one. / comments
Hello,
Can I just clarify what you would like to do? Are you talking about moving the installation of the SQL Monitor web front end into your DMZ, installing a second web front end in the DMZ, or ...