Page tree

IDERA SQL Inventory Manager constantly discovers SQL Server instances so you can select the ones that you want to monitor. When you open the Add SQL Server Instance wizard, you can choose those ones you want to register with IDERA SQL Inventory Manager; however,  you can also import a list of instances from your computer. Go to the Administration tab, on the Instances section you can find the option Import SQL Servers. Use this option to import a .csv file from your computer. 

Acceptable .csv format

You must use a properly-formatted .csv for each kind of instance you want to import. There are no limits on the number of rows included in the file, but note that if a row is incorrectly formatted, IDERA SQL Inventory Manager imports all rows above the incorrect row but does not import the incorrect row or any of the rows below that row. 

For users who must use a fully qualified domain name (FQDN) instead of the Windows Internet Naming Service (WINS), IDERA SQL Inventory Manager accepts the FQDN name for import and will collect information for that SQL Server instance. However, if you also add this instance as WINS, then realize that you have two records pointing to the same instance. IDERA SQL Inventory Manager does allow you to connect to the same instance using FQDN or WINS. If you don't want to have WINS instances, set the instances to Ignore. You can view ignored instances on the Instances > Ignored tab.

On-Premise instances

For importing On-premises SQL Server instances, please use the on-premises template or use the following general rules and .csv file format.

  • Enter or Browse SQL Server Instances cannot be null.
  • Owner should be unique across an instance.
  • Location should be unique across an instance.
  • The next time the user uploads a record for the same instances, the Instance Tags / Database Name / Database Tags should be added to the existing IDERA SQL Inventory Manager data. But the Instance Owner and Instance Location should be updated with the new values.
  • Comments
  • Current Tags
  • Add New Tag
Enter or Browse SQL Server InstancesOwnerLocationCommentsCurrent TagsAdd New Tag


















Amazon instances

For importing amazon SQL Server instances, please use the SQL Inventory Manager import template for AWS instances or use the following general rules and .csv file format.

  • Enter or Browse Amazon SQL Server Instances
  • Owner
  • Location
  • Comments
  • Current Tags
  • DataBase Name
  • Add New Tag
  • AWS Account Name
  • AWS Access Key
  • AWS Secret Key
  • AWS Region Endpoint
Enter or Browse Amazon SQL Server InstancesOwnerLocationCommentsCurrent TagsDataBase NameAdd New TagAWS Account NameAWS Access KeyAWS Secret KeyAWS Region Endpoint

































Azure instances

For importing On-premises SQL Server instances, please use the SQL Inventory Manager import template for Azure instances or use the following general rules and .csv file format.

  • Enter or Browse Azure SQL Server Instances
  • Owner
  • Location
  • Comments
  • Current Tags
  • DataBase Name
  • Add New Tag
  • Azure Account Name
  • Azure Tenant ID
  • Azure Client ID
  • Azure Client Secret Key
  • Azure Subscription ID
  • Account Type
Enter or Browse Azure SQL Server InstancesOwnerLocationCommentsCurrent TagsDataBase NameAdd New TagAzure Account NameAzure Tenant IDAzure Client IDAzure Client Secret KeyAzure Subscription IDAccount Type
ABC_1Group1West
"InstProd, Production, 24Hour"
Test"X, A, C"




ABC_1Group1West
"InstProd, Production, 24Hour"
DB2"DBA, ProductionDB, TESTDB"




XYZOwner,
,
,,




Importing a .csv file

To import a file:

  1. Select what type of instances you want to import, either Private/On-Premise , Amazon , or Azure.
  2. Click Browse to choose a properly formatted  .csv file from your computer.
  3. Go to C:> Program Files> Idera> SQLInventoryManager> CollectionService, either OnPremise , Amazon , or Azure. IDERA SQL Inventory Manager displays the instances from your uploaded .csv file.
  4. Select or clear those instances that you want to import, and then click Import.

CSV files

Keep in mind that the .csv files you use to import must have only the names of the instances.

Making bulk changes after importing instances

After importing the instances, you can use the bulk options available on the Managed Instances view to set the credentials for monitoring them, as well as editing their owners, locations, comments, and tags.

In the .csv file format, there is no separate column for credentials. However, after importing, you can update these instances using a bulk action to edit the credentials for all affected instances.

For example:

  • In the .csv file, add a Instance Tag called something such as "SQL creds" to all instances where SQL Server credentials should be used.
  • Import the .csv file.
  • Once the instances are imported, view your instances on the Managed Instances tab.
  • Filter the list of instances using the Instance Tag you added, i.e. "SQL creds".
  • Select all of the instances, and then use the bulk action Edit Credentials to set the SQL Server credentials on all of the instances.