Comments
Sort by recent activity
Thanks for the suggestion - I will add it to the feature request list. / comments
Thanks for the suggestion - I will add it to the feature request list.
Hi Gary,
I'm afraid I don't think that's possible - SQL server doesn't support it (i.e. you can't go from a later version to an earlier one). / comments
Hi Gary,
I'm afraid I don't think that's possible - SQL server doesn't support it (i.e. you can't go from a later version to an earlier one).
Sorry - I managed to type my own name wrong there :oops: Thanks for getting the logs to me. / comments
Sorry - I managed to type my own name wrong there :oops: Thanks for getting the logs to me.
You can send it to nigel.morse @ red-gate.com. Thanks
EDIT: managed to type my own name wrong... :roll: / comments
You can send it to nigel.morse @ red-gate.com. Thanks
EDIT: managed to type my own name wrong... :roll:
Sorry - that will be on the alert repository machine - actually now I think about it this was changed for release so it now goes under All Users so it should be in...
C:\Documents and Settings\All Users\Application Data\Red Gate\Logs\SQL Response Alert Repository 1 / comments
Sorry - that will be on the alert repository machine - actually now I think about it this was changed for release so it now goes under All Users so it should be in...
C:\Documents and Settings\All ...
Hi,
The Beta settings shouldn't be affecting the release it it just used the service account as the account to login with (and as you couldn't find the old
service then it can't be that).
Just to clarify - SQL Response cannot use different Windows accounts for the SQL connection, it has to be the account that is running the service. It can use different accounts for the WMI connection however. If you look in the log file in C:\Documents and Settings\<user name>\Local Settings\Application Data\Red Gate\Logs\SQL Response AlertRepository then you should see the errors being generated which should help us determine what the problem is. / comments
Hi,
The Beta settings shouldn't be affecting the release it it just used the service account as the account to login with (and as you couldn't find the old
service then it can't be that).
Just to c...
Thanks for reporting - we'll try and reproduce that here. / comments
Thanks for reporting - we'll try and reproduce that here.
You'd need multiple repositories (one behind each firewall) as we use WMI to talk to the servers, which itself uses DCOM which doesn't like firewalls (and especially not NAT).
There is some information that MS have here - http://msdn.microsoft.com/en-us/library/aa389290(VS.85).aspx but if the servers themselves use NAT'd addresses then DCOM doesn't work as it encodes the server address in the packets.
As for the client/repository connection you can chose which port to run the service on so that's a little easier to try and get opened.
With 1.0 I'm afraid there's no way to move the data around. / comments
You'd need multiple repositories (one behind each firewall) as we use WMI to talk to the servers, which itself uses DCOM which doesn't like firewalls (and especially not NAT).
There is some informa...
The check _should_ be running every 0.1 hours - however it would appear not to be!
There was an issue in the RC whereby some times parts of the monitoring would stop and not restart which should be fixed for the release. Could you try restarting the repository and see if that fixes the issue? / comments
The check _should_ be running every 0.1 hours - however it would appear not to be!
There was an issue in the RC whereby some times parts of the monitoring would stop and not restart which should be...
Hi Bern,
You need to install the client on your own machine for the URL to work - you should be able to connect the client to the repository on the test server then. The links can only bring up the client on the same machine. / comments
Hi Bern,
You need to install the client on your own machine for the URL to work - you should be able to connect the client to the repository on the test server then. The links can only bring up th...