Troubleshooting

Profiling local SQL Server stored procedures and user defined functions results in blank reports

noreply@blogger.com (Milena Petrovic) — Fri, 20 Apr 2012 17:07:00 +0000

Applies to
ApexSQL Profile

Symptoms
Profiling a stored procedure/user defined function on a local SQL Server can result in a blank report if the accounts used are not configured correctly

Resolution
1. Stored procedures and functions cannot be profiled if the SQL Server runs under a built-in account
2. The account under which the SQL Server runs has to be a member of the Local Administrators group

About ApexSQL Profile
ApexSQL Profile is a SQL Server Management Studio add-in which allows performance profiling of stored procedures and user defined functions. It tracks SQL code performance at the line level and generates comprehensive reports containing statement execution times, variable and parameter changes and more. For more information visit the ApexSQL Profile product page

Last updated
April 4, 2012

What should I do when I encounter freezing in ApexSQL Version?

noreply@blogger.com (Dorotej) — Thu, 05 Apr 2012 10:24:00 +0000

Applies to
ApexSQL Version

Summary
This article explains what to do when ApexSQL Version fails to respond

Symptoms
ApexSQL Version fails to respond and does not recover

Resolution
Please contact support@apexsql.com, describe the problem and provide as many information as you can.
If possible, send us a screenshot depicting the problem.

Last updated
April 05, 2012

Profiling remote SQL Server stored procedures and user defined functions results in blank reports

noreply@blogger.com (Milena Petrovic) — Mon, 26 Mar 2012 15:56:00 +0000

Applies to
ApexSQL Profile

Symptoms
Profiling a stored procedure/user defined function on a remote SQL Server can result in a blank report if the accounts used are not configured correctly

Resolution
To set up remote profiling:
1. Verify that both the local and the remote machines are in the same workgroup/domain
2. Configure the firewall of the remote SQL Server machine:
• Make sure that TCP/IP port 135, UDP port 4500 and UDP port 500 are open. If this requirement is not met, you may receive a CoUnmarshal exception
• Make sure the sqlserver.exe is added to the firewall’s exception list
3. Configure the local security settings on the remote machine:
• Log on using and administrator account
• In Control Panel, click Administrative Tools
• Go to Local Security Policy
• Open Network Access: Sharing and Security model for local accounts
• Set it to Classic – local users authenticate as themselves

If the remote machine is also a domain controller:
• Log on using an administrator account
• Open the Group Policy Management in Microsoft Management Console
• Expand the Group Policy Objects node
• Right click Default Domain Policy and select Edit

• In the Group Policy Management Editor, expand the Computer Configuration node and navigate to Windows Settings | Security Settings | Local Policies
• Select Security Options

• Navigate to Network access: Sharing and security model for local accounts. Double click the policy or right click and select Properties

• Check Define this policy setting check box and click OK

4. To configure the account that runs the remote SQL Server service:
• Open SQL Server Configuration Manager
• Navigate to SQL Server Services
• Double-click the SQL Server instance service
• In the SQL Server Properties dialog that will open, select This account and provide the credentials for a user account which is member of the Local Administrators group on both the local and the remote machine and click OK

Once this configuration takes effect, you will be able to profile stored procedures and functions on the remote SQL Server

Please note:
1. Stored procedures or functions residing on a remote SQL Server cannot be profiled if the SQL Server runs under a built-in account
2. The account under which the remote SQL Server runs has to be:
a. A member of the Local Administrators group on the computer running the SQL Server
b. A member of the Local Administrators group on the computer used to initiate the profiling
3. The security configuration listed above must be applied to each remote SQL Server instance where the stored procedures/functions which should be profiled reside

About ApexSQL Profile
ApexSQL Profile is a SQL Server Management Studio add-in which allows performance profiling of stored procedures and user defined functions. It tracks SQL code performance at the line level and generates comprehensive reports containing statement execution times, variable and parameter changes and more. For more information visit the ApexSQL Profile product page

Last updated
March 28, 2012

"Invalid activation code" message appears during Automatic and Manual activation

noreply@blogger.com (Dorotej) — Wed, 07 Dec 2011 15:45:00 +0000

Applies to
All ApexSQL Products

Summary
This article explains what to do when "Invalid activation code" message appears during both Automatic and Manual activation

Resolution
1) Go to Manual activation (Website login is required)

2) Select ApexSQL product in the Product list

3) Enter the Activation Key and Hardware ID an click Submit

4) The Activation code will be displayed. Click Get Reg key file

5) Save the file on the machine where ApexSQL product that should be activated is installed

6) Double click the saved reg file and, when prompted, allow the file to be added to the registry

7) A message notifying you about successful key adding to the registry will be displayed

About ApexSQL

ApexSQL is a leading provider of SQL Server tools for database recovery, database auditing, database comparison, documentation as well as SQL Server Management Studio and Visual Studio add-ins for SQL code refactoring, code completion and database source control. We strive to ensure that every one of our tools is standard-defining product in its class, from feature set, to performance, interface and quality.