![]() ![]() Database size details, creation date, and path.Connections to that DB instance (connection details available for each connection).Databases on that instance (each clickable for individual DB connection & size stats).On the "View Database Instance" screen, you will see lists containing the following items: Available SQL database instance information From the details view, you can simply click the "Services" tab to view a list of services, and can then click on the Microsoft SQL Server instance in that list. Results are also available by browsing to the discovered Windows server instance's CI either search for the device from the dashboard, via "Devices -> All Devices", or view your discovery job's results / score page and jump to the servers from there:Ĭlick any of the "device names" (right hand side) to jump to each discovered machine's details view. Another way to view SQL Database details Scroll to the bottom, and click the database instance name to view database details:įor a rundown of the database details discovery provides, jump to the "Available SQL database instance information" section. You can see the newly discovered SQL Server instances in the example below - Click any one of the Application Component Names for more details: If you don't see your SQL Server instances right at the top of the list, you can search for "SQL" to narrow the list down. Head to the Device42 main menu, Apps menu -> Application Components. There are a couple different ways to see the database details the most direct is via the discovered MSSQL Application components themselves. Viewing MSSQL discovery job results ģ) Once the job finishes, you can view the results of your database discovery. You can see the status of the discovery job on the job's setup page, as well - Scroll down to the "Job Status" section and look for the bar graphs. As MSSQL databases are detected, discovery will import a list of all instances, databases, and connection details. Subsequent job runs use the last successful credential and then the remaining credentials in the ordered list.Ģ) Kick off your new discovery job to test it (select "Run now" on the Job Screen). When the job runs, it will use the credentials in the order in which you enter them, stopping at the first successful authentication. You can enter an ordered list of preferred Discovery Target(s) Credential(s) when you create a database discovery job. Select Allow Unencrypted Connections if you want to discover MSSQL 2005 or MSSQL 2008 databases.īe sure to fill out both sets of credentials – the first set ( Database Username / Password) to authenticate to the Microsoft SQL database itself and the second ( Discovery Targets Credentials) to authenticate to the Windows server itself (like you’re used to for regular Windows-based discovery targets). Setting up your MSSQL discovery job ġ) To begin discovering your MSSQL Databases, create a new Windows discovery job and be sure to enable database discovery by checking the Collect database server information checkbox. Note: The discovery user must belong to the administrators user group to discover databases successfully. The snippet shown below is necessary to get data from some of the preceding views even if the user has read permissions ( sys.master_files, for example).ģ grant VIEW any DEFINITION TO For discovery to return detailed info about your database instance, you will require read permissions to the following system views: In order to query the below tables, please ensure you have View Server State permissions. Minimum Permissions Requirements for MSSQL Discovery Ensure these credentials have appropriate permissions to view the databases you are interested in discovering.ĭevice42 supports autodiscovery on Windows and *nix platforms for the following MSSQL versions. Microsoft SQL Server (MSSQL) discovery is supported on discovery targets running Microsoft Windows, and requires a separate set of credentials to authenticate to the database instance itself. MS SQL Server DB Discovery (on Windows targets) ![]() You can also use Database Connections Discovery jobs (see below) to discover databases. During database discovery, Device42 will identify and connect through the discovered active listening port. ![]() Contact licensing assistance.Īs of v16.17.00, Device42 supports MSSQL and Oracle database discovery for customers that have database instances configured to listen on non-standard ports, especially on a shared database server hosting multiple instances. Go to Tools > Settings > Licensing to see if the license is enabled. Note: Database discovery requires an Application Dependency Mapping license. Database Discovery About Database Discovery ĭatabase discovery was introduced in v16.02.00 (ensure you are running v16.02+), and currently supports Windows and *nix-based discovery jobs to discover Microsoft SQL (aka MSSQL), Oracle, Postgres SQL, and DB2 databases. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |