User profile for Nigel Morse

Hi Bern, The way it should work is that when you first run the client it registers the sqlresponse:// URL type. So when you get an email and click on the link it should fire up the client, connect to the alert repository then download and display the alert in question. So when you click on the link it just opens "My Documents" yes? Presumably this is on a machine where you have run the client at least once? What OS are you running (Vista, XP, Win2k etc). / comments

Hi Bern, The way it should work is that when you first run the client it registers the sqlresponse:// URL type. So when you get an email and click on the link it should fire up the client, connect...

0 votes

:oops: A late breaking fix has been added for final release [image] / comments

:oops: A late breaking fix has been added for final release

0 votes

There should be an error in the repository logs - which you can get from the system menu (click the icon top left of the client) / comments

There should be an error in the repository logs - which you can get from the system menu (click the icon top left of the client)

0 votes

This is because your SQL Server's error log is long. Response needs to read the errorlog to look for various things. The only way to do this is sp_readerrorlog which reads the entire log every time - Response then ignores everything it saw before and looks at the remainder. The way to avoid this would be to have a job that calls "sp_cycle_errorlog" periodically (e.g. daily - depending on how fast it grows). / comments

This is because your SQL Server's error log is long. Response needs to read the errorlog to look for various things. The only way to do this is sp_readerrorlog which reads the entire log every ti...

0 votes

Sorry you've had problems - I believe there was an issue with the RC in that if it failed to contact a SQL Server for some reason then when the server came back up it didn't correctly restart the monitoring. This is fixed for the final release. However could you send me the log files so I can have a quick check? They are at this location C:\Documents and Settings\[user name]\Local Settings\Application Data\Red Gate\Logs or alternatively you can click on topmost left hand corner on the SQL Response client icon menu and then use 'Copy Alert Repository Log Files' - and send them to nigel.morse @ red-gate.com / comments

Sorry you've had problems - I believe there was an issue with the RC in that if it failed to contact a SQL Server for some reason then when the server came back up it didn't correctly restart the m...

0 votes

Thanks - seems a reasonable request [image] I'll add this to the tracking system. / comments

Thanks - seems a reasonable request I'll add this to the tracking system.

0 votes

Hi, Such a button was on the plan, but sadly we didn't get to implement it in this version. / comments

Hi, Such a button was on the plan, but sadly we didn't get to implement it in this version.

0 votes

lewismoten wrote: Does each person using SQL Alert client need to also license each server, or are the servers licensed with the repository itself that the clients connect to? The servers are licensed with the repository and the client itself doesn't need a license / comments

lewismoten wrote: Does each person using SQL Alert client need to also license each server, or are the servers licensed with the repository itself that the clients connect to? The servers are ...

0 votes

Hi, lewismoten wrote: Some of the database servers that I administrate here have up to four instances of SQL running on the same server. From what I can see in the user interface, it appears that we will be charged a fee per server, per instance when this product comes out of beta. Is this assumption correct? Not quite - it's only per computer. So 4 instances on 1 computer is 1 license. lewismoten wrote: When I took a look at what happens when I choose the option to activate a server License, it prompts me to activate SQL Response with a serial number instead of specifying a server name/instance to activate. In the release it should be clear which server is selected (or you can right click on an instance to activate.) This will then activate all instances on that same computer. lewismoten wrote: What kind of pricing structure would be involved with this tool in the future? I already have a license that we renew each year for the SQL Toolkit. Will I need to make a request to management to justify additional licenses per server/instance as well? Is their a limit to how many servers that the repository service can monitor? Can multiple repository servers report back to a central repository to aggregate the logs? Many questions! [image] Future pricing is not something I would have to defer to marketing and sales on. On how many servers you can monitor it's a how long is a piece of string question. There is no fixed limit and it all depends on how busy the monitored servers are and how beefy the machine running the repository is. I would expect 50 instances to be a reasonable figure, but you may find you could get more out of it. Currently each repository runs alone with no aggregation - but each one can send emails and there's no limit to how many clients you can run and connect one to each repository / comments

Hi, lewismoten wrote: Some of the database servers that I administrate here have up to four instances of SQL running on the same server. From what I can see in the user interface, it appears that ...

0 votes

Hi Bern, We've half done what you ask for final release - namely the CPU time and memory usage. Sadly I think we just ran out of time for the sorting [image] / comments

Hi Bern, We've half done what you ask for final release - namely the CPU time and memory usage. Sadly I think we just ran out of time for the sorting

0 votes

How can we help you today?

Nigel Morse

Comments