Changing SQL discovery Port

[#1]

How & where do I change the port that sql discovery is using, to discover sql database names?

[SlightlyLoony]

There are actually no port numbers involved in discovering SQL servers (or any other application). Discovery finds SQL servers by looking for running processes with a particular name (in this case, "sqlservr.exe"). This behavior is controlled by the Classification table (navigate to Discovery -> Classification); in that list you'll see an entry for Microsoft SQL Server where this value is defined. That should discover all Microsoft SQL servers, no matter what port they're listening on. However, it's possible that you have a version of Microsoft SQL with a different process name. If that's the case, just add another Classification Criteria to the entry for Microsoft SQL Server, with the name of the process for the version you have -- and then let us know, so we can include it for other people!

As for the database name: the Discovery product does not yet ferret out the database name. That feature is on the list for a future release.

[#3]

" Can you discover Databases without database specific credentials?
Yes. There are two types of discovery that occur:

First, the presence of a database server can be identified through well-known listening TCP ports (1521 for Oracle or 3306 for MySQL for example).
Second, with credentials to the machine (not the database), the presence of the database server and databases are discovered through running processes and file system scans.
Database discovery with credentials
With proper JDBC credentials, the databases (table spaces for Oracle) and tables are discovered. "

Any comment?

[SlightlyLoony]

You caught some things that were just plain not correct, Alan -- thanks! I've edited that Wiki page to remove those references. Discovery actually works exactly as I described it earlier in this thread...