https://mbs.microsoft.com/customersource/support/documentation/systemrequirements
B , GP SP
https://mbs.microsoft.com/customersource/support/downloads/servicepacks
C, Posting table for posting slow performance
If you experience performance issues when you post, run the following SELECT statement on the PJOURNAL table. Run the statement against all the company databases.
SELECT * FROM PJOURNAL
If rows are returned, we recommend that you clear the contents of the table by running the following statement against all the company databases.
DELETE PJOURNAL
D, Enable delete Pjournal Job
INTRODUCTION
This article describes how to use Microsoft SQL Server Enterprise Manager to enable the Delete PJournal job that is created during the installation of Microsoft Dynamics GP or of Microsoft Business Solutions - Great Plains. When you enable the Delete PJournal job, the speed of the posting process in the program increases.
MORE INFORMATION
To enable the Delete PJournal job in Enterprise Manager, follow these steps: 1. Click Start, click Programs, click Microsoft SQL Server, and then click Enterprise Manager.
2. Expand Microsoft SQL Servers, expand SQL Server Group, and then expand the instance of SQL Server for Microsoft Dynamics GP or for Microsoft Business Solutions - Great Plains.
3. Expand Management, expand SQL Server Agent, and then click Jobs.
4. Right-click Remove Posted PJournals for your company database, and then click Properties.
5. Click to select the Enabled check box, click Apply, and then click OK.
Note By default, this job is specified to run every 30 minutes. You can change the frequency and the time of the job execution. To do this, follow these steps:1. Right-click Remove Posted PJournals for your company database, and then click Properties.
2. Click the Schedules tab.
3. Click Edit.
E, Performance issues that occur when you open windows.
1. Open the user preferences. To do this, follow the appropriate step:• In Microsoft Dynamics GP 10.0, click Microsoft Dynamics GP, and then click User Preferences.
• In Microsoft Dynamics GP 9.0 and in earlier versions, click Tools, point to Setup, and then click User Preferences.
2. Click AutoComplete.
3. Click to clear the Show AutoComplete Suggestions check box, and then click OK.
4. In Windows Explorer, delete the AutoCmpl.dat file and the AutoCmpl.idx file. These files are in the following folders: • In Microsoft Dynamics GP 10.0, the files are in the following location:
Document and Settings\username\Application Data\Microsoft Business Solutions\Microsoft Dynamics GP\dbname\
• In Microsoft Dynamics GP 9.0 and in earlier versions, the files are in the following location:
Document and Settings\username\Application Data\Microsoft Business Solutions\Great Plains\dbname\
5. Repeat step 1 through step 5 for each user.
F, Performance issues that occur when you log on to Microsoft Dynamics GP
Performance issues that occur when you log on to Microsoft Dynamics GP
1. Make sure that you have Microsoft Dynamics GP 9.0 Service Pack 2 or a later version installed. Logon issues were caused by an issue in which the Menu Master table (SY07110) became too large. To obtain the latest service pack for Microsoft Dynamics GP, visit the following Microsoft Web site:
https://mbs.microsoft.com/customersource/support/downloads/servicepacks/microsoftdynamicsgp90_mspreleases.htm?printpage=false
2. The location of the modified Reports.dic file and the modified Forms.dic file may affect the logon performance. If the modified dictionaries are on a network share, copy the dictionaries to the local Microsoft Dynamics GP folder, and then try to log on. To do this, follow these steps:a. To verify the location of the modified dictionaries, locate the Microsoft Dynamics GP folder. By default, this folder is in the following location:
C:\Program Files\Microsoft Dynamics\GP
b. Right-click the Dynamics.set file, and then open the Dynamics.set file in a text editor such as Notepad or WordPad.
c. Locate the path of the Reports.dic file and of the Forms.dic file. If the path is located on a network share, change the path to a local path.
3. Certain SmartList reminders may cause logon issues, depending on the homepage role for that user. To verify the reminders for a user, use the appropriate step:• In Microsoft Dynamics GP 9.0, click View, and then click Reminders. At the bottom, click Change Reminder Preferences. Remove any reminders in the Custom Reminders section at the bottom of the window.
• In Microsoft Dynamics GP 10.0, click Microsoft Dynamics GP, and then click Reminders. Click Change Reminder Preferences, and then remove the reminders in the Custom Reminder section at the bottom of the window.
G, Virus Scanner , exclude SQl database files and GP files and location
H, Sources of additional troubleshooting information
The System Information tool
Run the System Information tool to obtain the hardware specifications of the following computers: • The computer that is running SQL Server
• The client workstations
• The computer that is running Terminal Server
To obtain this information, follow these steps on each computer:1. Click Start, click Run, type msinfo32, and then click OK.
2. Click File, and then click Save to save this information to a file.
Trace logs
Create a Dexsql.log file and a SQL trace when you reproduce the performance issue. For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
850996 How to create a Dexsql.log file for Microsoft Dynamics GP
857246 How to create a SQL Trace with Profiler on Microsoft SQL Server 2000
To enable additional tracing, use SQL Query Analyzer to run the following script against the master database.
DBCC Traceon (1204,3605 -1)
Note This trace flag captures more information about deadlocks in the SQL Server error logs. To view the SQL Server error logs, start SQL Enterprise Manager. Click Management, and then click SQL Server Logs
H, SQLDIAG diagnostic tool
TechKnowledge Content
The information in this document applies to:
- Great Plains on Microsoft SQL Server
SUMMARY
This article describes the SQLDIAG tool and what it is used for.
MORE INFORMATION
The SQLDIAG tool gathers and stores diagnostic information into \MSSQL7\LOG\SQLDIAG.txt (Microsoft SQL Server 7.0) or \Program Files\Microsoft SQL Server\MSSQL\LOG\SQLDIAG.txt (Microsoft SQL Server 2000). This output file includes error logs, output from sp_configure and additional version information. Sqldiag must be run on the server itself from an MS-DOS window.
The syntax for a DEFAULT instance of SQL Server is as follows:
sqldiag -U sa -P password
For example, if the Login ID is sa and the password is access, you would type the following at the DOS prompt:
sqldiag -U sa -P access
If you have a named instance of SQL Server, the following syntax is as follows:
sqldiag -U sa -P password -i Instance Name
For example, if the SQL Server instance was named SERVER\SQL2000, you would type the following at the DOS prompt:
sqldiag -U sa -P access -i SQL2000
You should now be able to locate the sqldiag.txt and view the diagnostic information. If the SQL Server is running, sqldiag gathers the following items:
- Text of all error logs
- Registry information
- dll version information
- Output from: sp_configure, sp_who, sp_lock, sp_helpdb_, xp_msver, sp_helpextendedproc, sysprocesses
- Input buffer SPIDs/deadlock information
- Server Diagnostics Report (processor list, memory report, services report, environment report, system report)
No comments:
Post a Comment