Comments
Sort by recent activity
ACL levels on the relay only allows specific machines to send email through it. I had to put in a request just to permit the database server to send email. The repository is still setup on my local machine until a server can be setup for it. My local machine does not have access to send email through the SMTP relay. In addition, SMTP authentication uses digest authentication, so it's not your normal username/password authentication.
jerryhung wrote:
Interesting, because Database Mail goes through SMTP as well, no?
You can't simulate SQL Response as the DB mail account?
unless they block by IP, SMTP authentication should work with a set of username/password, and a valid FROM email address
/ comments
ACL levels on the relay only allows specific machines to send email through it. I had to put in a request just to permit the database server to send email. The repository is still setup on my local...
Thanks Chris. / comments
Thanks Chris.
The order of the table columns has not changed.
Although the scripts are structurally the same, they are not written out the same. I am running a file diff between the two versions in TFS.
I have had database builds where there has only been structurally 1 change in a stored procedure. However, TFS is showing that practically the whole database has changed due to the way that SQL Compare changes the order of scripted indexes, extended properties, etc.
This is making it hard for us to track down structural changes when looking at the history of individual objects, or the files checked in with a change set. / comments
The order of the table columns has not changed.
Although the scripts are structurally the same, they are not written out the same. I am running a file diff between the two versions in TFS.
I have h...
I have a similar situation where I have two domains. Essentially we will need to setup two individual repositories since each one authenticates with different credentials to access the servers. We have a service account in each domain that can access each SQL server instance in that domain in the same way.
I can see a need where you would want each individual instance to have separate login information to improve security. The only thing I can think of is a separate repository for each login credential since the repository uses the same account that it runs under to access each server that it monitors. That sounds like a nightmare to "make the rounds" when ever you want to check in on them with the SQL Response client.
I often leave a SQL Response client running throughout the day to keep tabs on alerts as they happen (don't have email setup yet). Setting an additional one up at the same time would start to get unmanageable.
Here is my feature request.
1. By default, if no login credentials are sepcified, let the repository connect to the SQL Server instance via the same credentials it uses to run as a service.
2. Allow windows login credentials to be specified per-instance. If login credentials are specified, then the repository will impersonate that account when querying against the SQL Server instance.
3. Allow a repository to query another repository for all of its logs. This would allow us to query one repository with SQL Response client rather than logging into many repositories.
4. Allow an SQL Response client to monitor multiple repositories.
5. Allow a repository to optionally store/share it's logs to an SQL database (problematic if the database is down) / comments
I have a similar situation where I have two domains. Essentially we will need to setup two individual repositories since each one authenticates with different credentials to access the servers. We ...
How about showing CPU% of each process? That would help me the most in tracking down the result of this problem. / comments
How about showing CPU% of each process? That would help me the most in tracking down the result of this problem.
Great.
If this does appear to happen again though, can you setup the install package to provide a warning first? Had I known, I would have waited until the network admin was available before I upgraded my client. / comments
Great.
If this does appear to happen again though, can you setup the install package to provide a warning first? Had I known, I would have waited until the network admin was available before I upgr...
Hippity, hip, hip, horray! [image] / comments
Hippity, hip, hip, horray!
I reset the "SQL Response Alert Repository Service", but I haven't seen any changes for a while now. Everything still states that it was last checked more than a day ago. / comments
I reset the "SQL Response Alert Repository Service", but I haven't seen any changes for a while now. Everything still states that it was last checked more than a day ago.
Thanks. I didn't try the others, but you may want to test and confirm that all other template modifications are used as well. [image] / comments
Thanks. I didn't try the others, but you may want to test and confirm that all other template modifications are used as well.
Thanks Nigel. I was seeing the same problems with 46 occurrences in the last hour alone. This may be a useful bit of information in the help file, or perhaps to add an alert/recommendation that the log file is getting to be too long. / comments
Thanks Nigel. I was seeing the same problems with 46 occurrences in the last hour alone. This may be a useful bit of information in the help file, or perhaps to add an alert/recommendation that the...