User profile for Dan J Archer

Update on SQL Response and the final release

Firstly, many thanks from the SQL Response team at Red Gate to all our beta testers. Youâ€™ve given us invaluable feedback over the last couple of months since SQL Response beta was released. I don...

0 followers 0 comments 0 votes

Hi Oleg, Thanks for that. All comments and critique are welcome. We don't currently have plans for gifts for beta testers, though we are offering a reward for people willing to talk to us by phone or in person in the UK regarding SQL Response. We're looking to conduct sessions of up to one hour. We're looking both for DBAs who are responsible for monitoring and maintaining SQL Servers, and might use a tool like SQL Response, but haven't touched SQL Response yet; and for users who have already had a chance to play with it. If anyone is interested, please e-mail usability@red-gate.com. Places are limited, but we are looking for quality feedback (not necessarily positive!) and those we talk to will receive a $100 Amazon voucher. Thanks, Dan / comments

Hi Oleg, Thanks for that. All comments and critique are welcome. We don't currently have plans for gifts for beta testers, though we are offering a reward for people willing to talk to us by phone ...

0 votes

Thanks for that, certainly a good idea - are there particular sorts would be of most use to you? Would you need to be able to sort by multiple columns at the same time (say by incident type, then by SQL Server), or just by one column at a time? Cheers, Dan / comments

Thanks for that, certainly a good idea - are there particular sorts would be of most use to you? Would you need to be able to sort by multiple columns at the same time (say by incident type, then b...

0 votes

Thanks for that, we did indeed consider this feature for the beta. We stopped short of it as one gets into the very interesting area of workflow: how much workflow should the tool have? Multiple users, assigning incidents like a bug tracking system; or integration with such systems; or just comments per issue? Any answers from people out there would be much appreciated. / comments

Thanks for that, we did indeed consider this feature for the beta. We stopped short of it as one gets into the very interesting area of workflow: how much workflow should the tool have? Multiple us...

0 votes

This is a very interesting discussion. I'd be very interested to know what configurations are typical for our customers, so if you do have issues in this area, or would like to comment further, please do. We definitely want to make it as workable as possible for people to use this tool the way they need to. / comments

This is a very interesting discussion. I'd be very interested to know what configurations are typical for our customers, so if you do have issues in this area, or would like to comment further, ple...

0 votes

It's a good point, and there are doubtless more cases where we can be of more help - we'll consider this one carefully. Cheers, Dan / comments

It's a good point, and there are doubtless more cases where we can be of more help - we'll consider this one carefully. Cheers, Dan

0 votes

Thanks for that, that's a good point. We're very interested in which incident types are good, which are bad, and any that are missing. All the best, Dan Archer Red Gate Software / comments

Thanks for that, that's a good point. We're very interested in which incident types are good, which are bad, and any that are missing. All the best, Dan Archer Red Gate Software

0 votes

Thanks for your feedback. Would you say this is useful even if you have no jobs scheduled to run on that server? Since, if there are jobs scheduled to run, then if the Agent is not running, you will be told the agent is not running - via "Job failed to start (Agent not running)" incident per job. / comments

Thanks for your feedback. Would you say this is useful even if you have no jobs scheduled to run on that server? Since, if there are jobs scheduled to run, then if the Agent is not running, you wil...

0 votes

Hi John, A very good question, and one we're still debating. We'd like to have more feedback from our beta users to understand what people need in this area, and why. One available solution in the beta is that if you really aren't worried by the disk space consumed by your dev machines, then after the disk space incidents come up you can hit "Ignore on <MACHINENAME>" to prevent them from coming up on that machine in the future. Thanks, Dan / comments

Hi John, A very good question, and one we're still debating. We'd like to have more feedback from our beta users to understand what people need in this area, and why. One available solution in the ...

0 votes

Hi Andrew, Thanks for your question. You're quite right, the Beta version of SQL Response does assume that you have such a login, and that all SQL Servers are on the same domain. Customers monitoring multiple domains can of course install one Incident Repository per domain, and connect to them sequentially using a single client. However, it sounds like your requirements are rather different. If SQL Response were to permit the user to specify a different Windows login for each server, would that satisfy your requirements? Or is Windows authentication not feasible between the Incident Repository computer and the monitored SQL Servers? If not on the same domain, are they on the same LAN? Are any protocols other than SQL communication open? All the best, Dan Archer Red Gate Software / comments

Hi Andrew, Thanks for your question. You're quite right, the Beta version of SQL Response does assume that you have such a login, and that all SQL Servers are on the same domain. Customers monitori...

0 votes

How can we help you today?

Dan J Archer

Activity overview