Installing Apexsql log 2010 Tags Apexsql, Log, Installing Applies to



Download 102.27 Kb.
Date conversion19.11.2016
Size102.27 Kb.
Installing ApexSQL Log 2010

Tags

ApexSQL, Log, Installing


Applies to

ApexSQL Log 2010


Summary

This article provides a detailed insight into the ApexSQL Log installation prerequisites and process. It discusses the hardware and software requirements, what is installed and where, different installation scenarios, and the permissions required to successfully install ApexSQL log.


Description
What are the hardware requirements?
CPU:

  • Pentium III 600 MHz or compatible and higher


RAM:

  • 256 MB (512 MB and higher recommended)


HDD:

  • 85 MB (100 MB and higher recommended)


What are the software requirements?
Operating systems:

  • Windows XP x32/x64

  • Windows Vista x32/x64

  • Windows 7 x32/x64

  • Windows 2003 x32/x64

  • Windows 2008 x32/x64

  • Windows 2008 R2 x32/x64


RDBMS:

  • SQL Server 2000 x32/x64

  • SQL Server 2005 x32/x64

  • SQL Server 2008 x32/x64

  • SQL Server 2008 R2 x32/x64


Note: Only experimental support is available for the IA64 versions of Windows and SQL Server
Other software components:

  • Microsoft ActiveX Data Access Objects Library (ADO) (MDAC) 2.8 or greater

  • Microsoft .NET Framework 2.0


What is installed?
ApexSQL Log consists of two types of components:

  • Client-side components

  • Server-side components


What are the client-side components and where are they located?
The client-side components are a set of executable, DLL and XML files that provide the user interface as well as a part of the applications functionality. You can choose the location where the bulk of it will be installed during the installation process. The default location is %Program Files%\ApexSQL\ApexSQLLog2010.

Additionally, in %AppDataLocal%\ApexSQL\ the following is stored:



  • In the ApexSQLLog2010 subfolder:

  • In the LOG subfolder:

    • Client-side application logs, which contain detailed information about the server and the database against which the application has been run, what has been run, etc.

  • In the LogData\\\ subfolder:

    • ApexSQLLog2010_*.acd – files that store database information that ApexSQL Log uses internally.

  • Options.xml – contains your saved project options

  • Layout.xml – contains information on the application layout

  • In the Common subfolder:

    • In the Updater subfolder:

      • ApexSQL Log.options – contains the updating options

    • Displayed Servers.xml – contains the list of SQL instances that you have added via the SQL Server List Management

    • Located Servers.xml – contains the list of SQL instances that are available, but haven’t been added yet


What are the server-side components and where are they located?
The server-side components are:

  • Database (optional):

    • APEXSQLLOG:

      • The default location where the tables that capture login, application and host information are stored.

      • Created if both conditions are fulfilled:

        • You chose to install the Connection Monitor

        • You didn’t specify where the Connection Monitor tables will be stored

  • DLL:

    • ApexSqlLogXprocs2010.DLL:

      • Referenced by the extended stored procedures

      • Located in the Microsoft SQL Server installation folder (by default %Program Files%\Microsoft SQL Server), \\Binn subfolder

  • Executable:

    • Located in the Microsoft SQL Server installation folder (by default %Program Files%\Microsoft SQL Server), \\Binn subfolder

  • ApexSqlLog2010Activation.exe - the executable used by ApexSQL Log to keep track of activation and evaluation states. 

  • ApexSqlLogApi2010Activation.exe - the executable used by ApexSQL Log API to keep track of activation and evaluation states.

  • ApexSqlLog2010ConnectionMonitor.exe – the executable component of the Connection Monitor

  • ApexSqlLog2010ServerHelper.exe - the executable used by ApexSQL Log extended procedures for tasks external to the SQL Server process.

  • ApexSqlLog2010ServerHelper.sys - the service executable used by ApexSQL Log extended procedures.


  • Extended stored procedures:

    • Located in the master database

    • Providing application functionality:

      • dbo.xp_ApexSqlLog2010

      • dbo.xp_ApexSqlLogApi2010

      • They provide:

        • The ability to audit transaction logs

        • Server-side auditing which significantly increases performance, especially on slow networks or VPN

    • Providing Connection Monitor functionality:

      • dbo.xp_ApexSqlLog2010ConnectionMonitor

      • dbo.xp_ApexSqlLog2010ConnectionMonitor_Disable

      • dbo.xp_ApexSqlLog2010ConnectionMonitor_Enable

      • dbo.xp_ApexSqlLog2010ConnectionMonitor_Info

      • dbo.xp_ApexSqlLog2010ConnectionMonitor_State

      • dbo.xp_ApexSqlLog2010ConnectionMonitor_Stop

  • Stored procedures:

    • dbo.sp_ApexSqlLog2010ConnectionMonitor_Start:

      • Starts the Connection Monitor

      • Located in the master database

  • Tables (optional):

    • Created if you choose to install the Connection Monitor

    • Located in the database you’ve selected during the installation process (APEXSQLLOG if you chose )

      • dbo.APEXSQL_LOG_CONNECTION_MONITOR_SESSION – stores:

        • The time the Connection Monitor session started

        • The time the Connection Monitor session finished

        • Name of the server where the Connection Monitor was running

      • dbo.APEXSQL_LOG_LOGIN - stores

        • The Server Process ID

        • The time the transaction occurred

        • The name of the application that initiated the transaction

        • The SQL or Windows user name

        • The users host name

How to install ApexSQL Log?

Since ApexSQL Log is a powerful client-server application the following should be taken into account before installing it:



  • Minimum Windows permissions to install the client and server-side components.

  • Minimum SQL permissions to install the server-side components.

  • Planning ApexSQL Log installation

  • Which installation scenario suits you and your environment the best?


What are the minimum Windows permissions required to install the client and server-side components?
In order to install ApexSQL Log, the account used to start the installation has to have administrative privileges.

If User Account Control (UAC) doesn’t exist or is disabled on your system, and the installation has been started from a non-administrative account the following error will be shown:



c:\users\heisenberg\documents\7fail.png

On the other hand, if UAC is enabled and the installation has been started from a non-administrative account you will be prompted to enter credentials for an administrative account, as shown:





NOTE: You have to start the installation using administrative account/supply administrative credentials. The installation will fail, even if started from a power user account/power user credentials are supplied. There is an exception to this behavior, when Group Policy is used to deploy the application to target computers in an Active Directory domain; however, that scenario is beyond the scope of this article.
What are the minimum SQL permissions required to install the server-side components?
Extended stored procedures are essential parts of ApexSQL Logs architecture. They are stored in the master database. By SQL server design, only a member of the sysadmin SQL Server role is able to create and register them. Therefore, the account you want use to authenticate to the SQL server during the installation process has to be a member of the sysadmin SQL Server role.
Planning ApexSQL Log installation
Planning is integral for a successful and trouble-free installation of any software. We recommend you to take a few minutes and think about the following:

  • Do you meet the hardware and software requirements stated in this article?

  • Which installer do you plan to use?

  • Do the databases you want to audit reside on a local or a remote SQL server? Do they reside in a SQL cluster?

    • If the SQL server is remote, how do you access it? Do you use a LAN, broadband or VPN connection? How fast is it?

  • Are you a part of a network? If so, is it a workgroup or a domain?

  • Which Windows user account will you use to start the ApexSQL Log installation process?

    • Does it have administrative privileges over the computer where the client application will be installed?

  • How do you plan to authenticate to the SQL server during the installation process? Windows or SQL authentication?

    • If you plan to use Windows authentication:

      • Does the user account have administrative privileges over the computer where the SQL server is installed?

      • Is it a member of the sysadmin role in the SQL Server where the databases you want to audit reside?

    • If you plan to use SQL authentication:

      • Is the SQL login member of the sysadmin role?

      • Does the user account used to start the installation have administrative privileges over the computer where the SQL server is installed?

  • Do you plan to capture the login information?

    • If so, where do you want to store the captured information?

Answering these questions can help you determine the installation scenario that will fit you and your environment.


What installation scenario suits you and your environment the best?
Different environments require different approaches to installation. Using an approach unsuitable for your environment might result in installation failure.
Using the ApexSQL Product installer:


      1. If all of the following requirements are met:




then:

  1. Follow the steps described here to install the client-side components

  2. Follow the steps described here to install the server-side components

    1. Select Windows authentication as described in step 7.

    2. Disregard steps 8. and 9. and proceed with step 10.




      1. If all of the following requirements are met:



  • You are logged in as an administrator on your local machine

  • The SQL server, where the databases you want to audit reside, is installed your local machine

  • The account you use to authenticate to the SQL server is a member of the sysadmin role

then:

  1. Follow the steps described here to install the client-side components

  2. Follow the steps described here to install the server-side components

  1. Disregard step 7.

    1. Select SQL authentication as described in step 8. and proceed with step 9.




      1. If all of the following requirements are met:



  • The SQL server, where the databases you want to audit reside, is installed on a remote machine

  • Your machine and the machine where the SQL server is installed are:

    • In the same domain and you are logged in as a domain administrator

    • In trusted domains and you are logged in as a member of the global domain administrator group

  • The account you are logged in to is a member of the sysadmin role on the SQL server

then:

  1. Follow the steps described here to install the client-side components

  2. Follow the steps described here to install the server-side components

  1. Select Windows authentication as described in step 7.

  2. Disregard steps 8. and 9. and proceed with step 10.


Using the individual installer:


        1. If all of the following requirements are met:



  • You are logged in as an administrator on your local machine

  • The SQL server, where the databases you want to audit reside, is installed your local machine

  • The account you are logged in to is a member of the sysadmin role on the SQL server

then:

  1. Follow the steps described here to install both the client and server-side components

  1. Select Use NT authentication as described in step 7.

  2. Disregard steps 8. and 9. and proceed with step 10.




        1. If all of the following requirements are met:



  • You are logged in as an administrator on your local machine

  • The SQL server, where the databases you want to audit reside, is installed your local machine

  • The account you use to authenticate to the SQL server is a member of the sysadmin role

then:

  1. Follow the steps described here to install both the client and server-side components

  1. Disregard step 7.

  2. Select Use SQL authentication as described in step 8. and proceed with step 9.




        1. If all of the following requirements are met:



  • The SQL server, where the databases you want to audit reside, is installed on a remote machine

  • Your machine and the machine where the SQL server is installed are:

    • In the same domain and you are logged in as a domain administrator

    • In trusted domains and you are logged in as a member of the global domain administrator group

  • The account you are logged in to is a member of the sysadmin role on the SQL server

then:

  1. Follow the steps described here to install both the client and server-side components

  1. Select Use NT authentication as described in step 7.

  2. Disregard steps 8. and 9. and proceed with step 10.




      1. If all of the following requirements are met:



  • The SQL server, where the databases you want to audit reside, is installed on a remote machine

  • None of the cases listed above apply to your environment fully

  • You can log on your local machine as an administrator

  • You can log on the machine where the SQL server is installed as an administrator

  • The user account you use to log on the machine where the SQL server is installed is a member of the sysadmin server role on the SQL server

then:

  1. Log on the local machine as an administrator

  2. Follow the steps described here to install the client components

  3. Log on the machine where the SQL server is installed as an administrator and copy the installer to it

  4. Follow the steps described here to install the server components

  1. Select Use NT authentication as described in step 7.

  2. Disregard steps 8. and 9. and proceed with step 10.




      1. If all of the following requirements are met:



  • The SQL server, where the databases you want to audit reside, is installed on a remote machine

  • None of the cases listed above apply to your environment fully

  • You can log on your local machine as an administrator

  • You can log on the machine where the SQL server is installed as an administrator

  • The account you use to authenticate to the SQL server is a member of the sysadmin role

then:

  1. Log on the local machine as an administrator

  2. Follow the steps described here to install the client components

  3. Log on the machine where the SQL server is installed as an administrator and copy the installer to it

  4. Follow the steps described here to install the server components

  1. Disregard step 7.

  2. Select Use SQL authentication as described in step 8. and proceed with step 9.

If none of the cases stated above applies to your environment, please talk to your system/database administrator to install ApexSQL Log for you or contact support@apexsql.com providing the details of your particular environment.



The installation process

You can install ApexSQL Log using the ApexSQL Products installer, that can be obtained from here, or using ApexSQL Log individual installer, that can be obtained from here.



If you are using the ApexSQL Products installer:

To install the client-side components:



  1. Double click apexsqlinstaller.exe to start the installation.

  2. Click Next.

axloginstall01.jpg

  1. Read the End User License Agreement, select I accept the agreement and click Next.

axloginstall02.jpg

  1. Choose the location that will contain the ApexSQL Log installation folder, and click Next. The default location is %Program Files%\ApexSQL, and ApexSQL Log is installed in the ApexSQLLog2010 subfolder.

axloginstall03.jpg

To change the default location, click Browse.



axloginstall04.jpg

In the Browse for Folder dialog box, specify the location, click OK and then click Next.



axloginstall05.jpg

  1. Select ApexSQL Log (Client) from the application list and click Next.

axloginstall06.jpg

  1. Select the Start Menu folder where the shortcuts will be placed. By default, they are placed in the ApexSQL folder. Click Next.

axloginstall07.jpg

To change the default location, click Browse.



axloginstall08.jpg

In the Browse for Folder dialog box, specify the location, click OK and then click Next.



axloginstall09.jpg

  1. Select whether you want to create Desktop and Quick Launch shortcuts and click Next.

axloginstall10.jpg

  1. Review your settings.

axloginstall11.jpg

  1. Click Back if you want to change any of the settings.

axloginstall12.jpg

  1. Click Install to start the installation process.

axloginstall13.jpg


  1. Select whether you want to start the application and click Finish.

axloginstall14.jpg
To install the server-side components:

  1. Start ApexSQL Log.

  2. Click the ellipsis button in the Project dialog that will be shown.

axloginstall36.jpg

  1. To get the list of available SQL instances, click Refresh in the SQL Server Management List.

axloginstall38.jpg

  1. From the Available SQL Server List in the SQL Server Management List dialog select the SQL instance where the database you want to audit resides and click Add.

axloginstall37.jpg

  1. Click OK.

axloginstall39.jpg

  1. Click on the Server field arrow in the Project dialog and from the drop-down menu select the SQL instance from the drop-down menu.

axloginstall40.jpg

  1. Select Windows Authentication to authenticate to the SQL server with your Windows user account.

axloginstall41.jpg

  1. Select SQL Server Authentication to authenticate to the SQL server using a SQL Server login and provide the user name and password.

axloginstall42.jpg

  1. Select the Store Encrypted Password option to save the SQL credentials.

axloginstall43.jpg

  1. Click on the Database field arrow in the Project dialog and select the database (whose transaction log you want to audit) from the drop-down menu.

axloginstall44.jpg

  1. Click Open.

axloginstall45.jpg

  1. Click Yes in the Install Server-side Components dialog that will be displayed.

axloginstall46.jpg
This will install the server-side components, including the Connection Monitor. The ApexSQLLog database will be created during this process. The Connection Monitor tables, dbo.APEXSQL_LOG_CONNECTION_MONITOR_SESSION and dbo.APEXSQL_LOG_LOGIN will be created within the ApexSQLLog database.

If you are using the ApexSQL individual installer:

To install the client application only:

  1. Double click apexsqllog.exe to start the installation.

  2. Click Next.

axloginstall15.jpg

  1. Read the End User License Agreement, select I accept the agreement and click Next.

axloginstall16.jpg

  1. Choose the location that will contain the ApexSQL Log installation folder, and click Next. The default location is %Program Files%\ApexSQL. ApexSQL Log will be installed in the ApexSQLLog2008 subfolder.

axloginstall17.jpg

To change the default location, click Browse.



axloginstall19.jpg

In the Browse for Folder dialog box, specify the location, click OK and then click Next.



axloginstall05.jpg

  1. Select the Client application (GUI and CLI) option from the drop-down menu and click Next.

axloginstall48.jpg

  1. Select the Start Menu folder where the shortcuts will be placed. By default, they are placed in the ApexSQL folder. Click Next.

axloginstall29.jpg

To change the default location, click Browse.



axloginstall30.jpg

In the Browse for Folder dialog box, specify the location, click OK and then click Next.



axloginstall09.jpg

  1. Select whether you want to create Desktop and Quick Launch shortcuts and click Next.

axloginstall31.jpg

  1. Review your settings.



  1. To change any of the settings click Back.



  1. Click Install to start the installation process.



  1. Select whether you want to start the application and/or view the README file and click Finish.



To install the server-side components only:

  1. Double click apexsqllog.exe to start the installation.

  2. Click Next.

axloginstall15.jpg

  1. Read the End User License Agreement, select I accept the agreement and click Next.

axloginstall16.jpg

  1. Choose the location that will contain the ApexSQL Log installation folder, and click Next. The default location is %Program Files%\ApexSQL. ApexSQL Log will be installed in the ApexSQLLog2008 subfolder.

axloginstall17.jpg

To change the default location, click Browse.axloginstall19.jpg

In the Browse for Folder dialog box, specify the location, click OK and then click Next.

axloginstall05.jpg


  1. Select Server-side components on a local server from the drop-down menu and click Next.

axloginstall49.jpg

  1. Specify the name of the SQL server instance/SQL cluster virtual name where the databases you want to audit reside, and click Next.

axloginstall22.jpg

  1. Select Use NT authentication to authenticate to the SQL server with your Windows user account and click Next.



  1. Select Use SQL Server authentication to authenticate to the SQL server using the SQL Server login and click Next. axloginstall24.jpg

  2. Provide the user name and password of the SQL login and click Next.



  1. Select Capture Login Information if you want to install the Connection Monitor. The Connection Monitor is a component which captures and associates login information such as the Windows user name, application name, host name etc. to the transaction records you want to view. Click Next.

axloginstall26.jpg

If you chose to install the Connection monitor:



  1. Select the database where you want the login information to be stored from the dropdown menu. If you don’t select a specific database, the installer will create a database named APEXSQLLOG. The login information will be stored in the dbo.APEXSQL_LOG_CONNECTION_MONITOR_SESSION and dbo.APEXSQL_LOG_LOGIN tables.

axloginstall27.jpg

  1. To maintain the login information automatically, select Automatic and specify for how many days the login information should be stored. Information older than the specified period will be auto-truncated. To maintain the login information yourself, select I will maintain the information myself and click Next.

axloginstall28.jpg

  1. Review your settings.



  1. To change any of the settings click Back.



  1. Click Install to start the installation process.



  1. Select whether you want to view the README file and click Finish.

To install both the client application and the server-side components at the same time:



  1. Double click apexsqllog.exe to start the installation.

  2. Click Next.

axloginstall15.jpg

  1. Read the End User License Agreement, select I accept the agreement and click Next.

axloginstall16.jpg

  1. Choose the location that will contain the ApexSQL Log installation folder, and click Next. The deafault location is %Program Files%\ApexSQL. ApexSQL Log will be installed in the ApexSQLLog2008 subfolder.

axloginstall17.jpg

To change the default location, click Browse.axloginstall19.jpg

In the Browse for Folder dialog box, specify the location, click OK and then click Next.

axloginstall05.jpg


  1. Select Client application (GUI and CLI) and server-side components on a local server from the drop-down menu and click Next.

axloginstall47.jpg

  1. Specify the name of the SQL server instance/SQL cluster virtual name where the databases you want to audit reside, and click Next.

axloginstall22.jpg

  1. Select Use NT authentication to authenticate to the SQL server with your Windows user account and click Next.



  1. Select Use SQL Server authentication to authenticate to the SQL server using a SQL Server login and click Next. axloginstall24.jpg

  2. Provide the user name and password of the SQL login and click Next.



  1. Select Capture Login Information if you want to install the Connection Monitor. The Connection Monitor is a component which captures and associates login information such as the Windows user name, application name, host name etc. to the transaction records you want to view. Click Next.

axloginstall26.jpg

If you chose to install the Connection monitor:



  1. Select the database where you want the login information to be stored from the dropdown menu. If you don’t select a database, the installer will create a database named APEXSQLLOG. The login information will be stored in the dbo.APEXSQL_LOG_CONNECTION_MONITOR_SESSION and dbo.APEXSQL_LOG_LOGIN tables.

axloginstall27.jpg

  1. To maintain the login information automatically, select Automatic and specify for how many days the login information should be stored. Information older than the specified period will be auto-truncated. To maintain the login information yourself, select I will maintain the information myself and click Next.

axloginstall28.jpg

  1. Select the Start Menu folder where the shortcuts will be placed. By default, they are placed in the ApexSQL folder. Click Next.

axloginstall29.jpg

To change the default location, click Browse.



axloginstall30.jpg

In the Browse for Folder dialog box, specify the location you want. Click OK and then click Next.



axloginstall09.jpg

  1. Select whether you want to create Desktop and Quick Launch shortcuts and click Next.

axloginstall31.jpg

  1. Review your settings.



  1. To change any of the settings click Back.



  1. Click Install to start the installation process.



  1. Select whether you want to start the application and/or view the README file and click Finish.



The database is protected by copyright ©dentisty.org 2016
send message

    Main page