You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

IDERA SQL Secure requires that you register any SQL Server instances that you want to monitor before auditing begins. The Register a SQL Server option allows you to add instances to SQL Secure one at a time. For environments having many SQL Server instances, a quick time saver is to import a .csv file. The Import SQL Servers option lets you quickly upload a file containing the ServerName, AuthType (0 = Windows Authentication, 1 = SQL Server Authentication), User, Password, UseSameCredentials (0 = false, 1 = true), WindowsUser, and WindowsUserPassword data for the instances in your environment that you want to audit. Once imported, new SQL Server instances are registered directly in the repository with default settings. If the SQL Server instance already exists in the repository, then SQL Secure updates the login credentials for the server.

After importing your SQL Server instances, be sure to go the the Server Group Tags view to add the new servers to tag for better management. For more information about tags, see Manage server group tags.

Acceptable .CSV format

You must use a properly-formatted .csv to successfully import a list of SQL Server instances. There is no limit to the number of rows included in the file, but note that if a row is incorrectly formatted, IDERA SQL Secure displays a message stating that the file is not in the proper format.

For a successful import of SQL Server instances, please use the following general rules and .csv file format.

  • Server Name. Name of the SQL Server you want to register.
  • Authorization Type. Type of SQL Server authentication used to connect to the audited SQL Server.
    • 0 = Windows authentication
    • 1 = SQL Server authentication
  • User.
    • If the authorization type selected is 0 (Windows authentication) , use Windows credentials. 
    • If the authorization type selected is 1 (SQL Server authentication) , use the default credentials of the SQL Server Agent.
  • Password. Password associated with the user account used previously.
  • Use Same Credentials.
    • TRUE = Use Windows credentials specified previously.
    • FALSE = Specify a different Windows account.
  • Windows User. Credentials used to gather information about the OS, AD objects.
    • If Use Same Credentials is TRUE (Use Windows credentials specified previously) , type a comma (,) in this column. 
    • If Use Same Credentials is FALSE (Specify a different Windows account) , specify a different Windows user account.
  • Windows User Password
    • If Use Same Credentials is TRUE (Use Windows credentials specified previously) , type a comma (,) in this column. 
    • If Use Same Credentials is FALSE (Specify a different Windows account) , specify the password for the different Windows user account.
Server NameAuthentication TypeUserPasswordUse Same CredentialsWindows UserWindows User Password
Server NameAuthTypeUserPasswordUseSameCredentialsWindowsUserWindowsUserPassword
FINSVR0myhouse\williamTest123TRUE,,
SQLSVR10thathouse\jimNum1DBAFALSEToolsTest123
SQLSVR21yourhouse\scottTestabc1FALSEToolsTest123

Sample .csv file:

Server Name,AuthType,User,Password,UseSameCredentials,WindowsUser,WindowsUserPassword
FINSVR1,0,myhouse\william,Test123,TRUE,,
SQLSVR1,0,thathouse\jim,Num1DBA,FALSE,Tools,Test123
SQLSVR2,1,yourhouse\scott,Testabc1,FALSE,Tools,Test123

The first row in the previous table must be included in the .csv file as shown.

Importing a .csv file

To import SQL Server instances:

  1. In the Security Summary view, click Import SQL Servers at the top of the Summary tab. Alternatively, you can go to File menu and select Import SQL Servers.
    OR
    In the Manage SQL Secure view, click Import SQL Servers at the top of the Repository Status window. Alternatively, you can go to File menu and select Import SQL Servers.
    The Import SQL Servers window opens.
  2. Locate the file you want to import. Note that the file must be in the .csv format.
  3. Click Open, and then click OK. SQL Secure validates the file format and displays the message, "Any registered servers found in the import file will have their credentials updated based on those specified in the file."
  4. Click OK.


SQL Secure manages SQL Server security and permissions.
  • No labels