How can we help you today? How can we help you today?
lewismoten

Activity overview

Latest activity by lewismoten

Feature Request: Relational Output Path
I would either like to feed a path into the command line utility, or have it specified in the project file "HtmlPath" to be relational to either the project file, current directory, or command util...
2 followers 2 comments 0 votes
Improved project file format.
My goal is to automate documenting all objects under tables, views, programmability, storage, and security within a single database catalog. In other words - document all objects within a single da...
1 follower 1 comment 0 votes
Feature Request - Alerts through Database Mail
SMTP mail is not an option for me at the moment with the current access control levels. However, one of the databases that I am monitoring has been granted access to send email to the relay. A data...
3 followers 3 comments 0 votes
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 ...
0 votes
Feature Request - Sort Indexes Alphabeticaly (Script Export)
I store the changes of schema information in TFS. Each time I export the schema objects as individual SQL scripts, many objects appear to change in structure. Upon closer examination, they were not...
2 followers 4 comments 0 votes
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...
0 votes