FAQ

EMS SQL Administrator is a powerful graphical tool for Microsoft SQL Server administration. It provides a complete and easy-to-use set of tools for administering SQL Server. SQL Administrator is designed specifically for database administrators and allows performing administrative tasks in the fastest, easiest and most efficient way.

First of all you must have an opportunity to connect to some local or remote Microsoft SQL Server. Besides you need your computer to satisfy the system requirements of EMS SQL Administrator.

  1. If your server is installed as named instance, use server name in form computer_name\instance_name. SQL Server Express Edition has the default SQLEXPRESS instance name.
  2. If you connect to the remote server, make sure that the connection is not blocked by firewall. Ask your system administrator to correctly open appropriate ports.
  3. Make sure that SQL Server is started and you have correct login to access it.
  4. Make sure that client protocols are correctly tuned. Use SQL Server Configuration Manager on connection to SQL Server 2005 or higher (it is installed with Native Client) or SQL Server Client Network Utility (system32\cliconfg.exe) on connection to earlier versions.
  5. Make sure that remote connection is enabled on server and server protocols are correctly tuned. Use SQL Server Surface Area Configuration on SQL Server 2005 or higher and SQL Server Network Utility (Program Files\Microsoft SQL Server\80\Tools\Binn\svrnetcn.exe) on earlier server versions.
  6. If you use named instance of server with dynamic TCP/IP port, make sure that SQL Server Browser service is running.
  7. If you connect remotely, try using server IP address instead of its name to ensure that DNS works well.

WMI connection is used to:

  • get system information about SQL server, e.g. installed operating system or CPU type
  • start and stop SQL Server services
  • view Windows event logs
  • get system performance counter values to display them in the product, in some alarms and for statistics collection.

You need to increase timeout values on the “Query tool” tab of the “Options” dialog, or set them to 0 - unlimited.

SQL Administrator stores all your settings in the Windows registry. It means that the only way to transfer your database data is to get access to the Windows registry. You can do it by loading OS from your old HDD (if possible) or by opening the registry file with a special editor program. If you managed it, you can unload the 'HKEY_CURRENT_USER\Software\EMS\SQL Administrator’ and 'HKEY_LOCAL_MACHINE\Software\EMS\SQL Administrator’ branches to the *.REG files, transfer these files to a new system and add information to the registry by double-clicking the files. Also you have to grant write permissions for 'HKEY_LOCAL_MACHINE\Software\EMS\SQL Administrator’ branch to ‘Users’ Windows group using Registry Editor tool.

Statistics Collector collects detailed performance statistics every 5 minutes by default. This information is stored 31 days by default and then averaged out. The collected values are averaged out by days of the week every 30 minutes. It is necessary to reduce the total amount of stored information. Statistics collection parameters can be set for each server on the "Statistics Collection" tab of the "Server Registration Properties" dialogue.

To create and edit maintenance plans you should install SQL Server Integration Services on your computer. Otherwise, you can view the existing maintenance plans only.
If SQL Server Integration Services are installed on another computer in your local network, using the 'Ssis11Adpt.exe' file and sample configuration files 'Ssis11Adpt.exe.config.example' and 'SsisClient.config.example' from the program installation folder, you can do the following:
  • copy the 'Ssis11Adpt.exe' file to the computer with SQL Server Integration Services installed
  • create the 'Ssis11Adpt.exe.config' file in the 'Ssis11Adpt.exe' folder and set parameters
  • launch 'Ssis11Adpt.exe'
  • create the 'SsisClient.config' file in the program folder and set parameters.
If the configuration files are set correctly, maintenance plans can be edited. Do not forget to open a port in Firewall.

Probably the maintenance plan job cannot be run. Please see the job execution history with <maintenance_plan_name> or <maintenance_plan_name>.<subplan_name> names.

Please check on the server where SQL Administrator repository database is located that the cleanup_alarm_log_<repository_database_name> job is running. It cleans the old log records.

Information on checking database and rebuilding/reorganizing indexes task executions is taken from the maintenance plan and job history. So, the task launches in the wizard and SQL command executions are not reflected in the “Last Execution Date” column.