I'll try to paste it the articles below.
Hope this helps. These articles haven't entirely resolved our issues. An underlying issue is that we are using Windows Authentication, and we think that the system database is being validated for every screen a user can have access to (?). We're still working with tech support on that one.
Gail J-N
Article : 947428
SYMPTOMS
Performance decreases when you start Microsoft Dynamics SL 7.0 through a remote session to Windows Server 2003 Terminal Server.
CAUSE
This problem occurs because Terminal Server deletes the .xml files that Microsoft Dynamics SL uses at startup when the remote session is closed. Every time that you establish a new remote session and then start Microsoft Dynamics SL, the .xml files are re-created. This behavior causes performance to decrease.
RESOLUTION
To resolve this problem, configure the terminal server not to delete the contents of the Temporary folder of the remote user when the remote session is closed. This action guarantees that the terminal server caches the .xml files. To do this, follow these steps: 1. Make that all user sessions to the terminal server are closed.
2. Click Start, point to Administrative Tools, and then click Terminal Services Configuration.
3. In the Terminal Services Configuration pane, click Server Settings.
4. In the Settings pane, right-click Delete temporary folders on exit, and then click No.
5. In the Settings pane, right-click Use temporary folders per session, and then click No.
6. Close the Terminal Services Configuration dialog box.
7. Restart the computer.
Article ID : 941009
SYMPTOMS
You experience slow performance in Microsoft Dynamics SL 7.0 when you try to perform any of the following actions:
• You try to log on to Microsoft Dynamics SL 7.0.
• You try to open a screen.
• You try to open a report.
Additionally, events that reference the .NET Runtime Optimization Service are logged in the Application log.
CAUSE
This problem occurs because the Microsoft .NET Framework 2.0 that Microsoft Dynamics SL 7.0 uses includes a process that checks for valid certificates on the Internet every time that an executable file is accessed. If the network is tightly secured or if Internet access is not easily available, this process causes slow performance in Microsoft Dynamics SL 7.0.
RESOLUTION
To improve performance, follow these steps:
1. Start Windows Internet Explorer.
2. On the Tools menu, click Internet Options.
3. On the Advanced tab, click to clear the Check for publisher's certificate revocation check box under Security.
4. Click OK.
Article ID : 939242
INTRODUCTION
This article describes how the global assembly cache (GAC) and the native image cache can improve performance in Microsoft Dynamics SL 7.0.
MORE INFORMATION
Global assembly cache
Each computer that has the .NET runtime installed has a code cache that is called the global assembly cache. The global assembly cache stores assemblies that are specifically designated to be shared by multiple applications that are installed on the computer. Microsoft Dynamics SL contains several designated shared assemblies that are put into the global assembly cache during the client installation process.
Native image cache
Each computer that has the .NET runtime installed has a native code area that is called the native image cache. The native image cache stores the files that contain compiled, processor-specific code on the computer. All the .NET assemblies are pre-compiled code that is not computer-specific. When the .NET assemblies are run, the just-in-time (JIT) compiler is run to change the assemblies into native, computer-specific code that will be run. The native image cache holds the compiled version of the assemblies. The native image cache also improves the load time performance of the screens in Microsoft Dynamics SL. All the Microsoft Dynamics SL applications are included in the native image cache only if the client elements and the server elements of Microsoft Dynamic SL are installed on the computer. The native image cache does not work on a network in a client/server environment. Therefore, to improve the screen load time performance, both the Microsoft Dynamics SL program files and the Microsoft Dynamics SL client files must be installed on the same computer.
Note After the installation of Microsoft Dynamics SL is completed, the files in the native image cache continue to be installed by a deferred execution service that runs while the computer is idle.
After the Microsoft Dynamics SL files are pre-compiled in the native image cache, you will notice an improvement in the load time performance of certain screens. The improvement varies based on a screen's file size. For example, you may experience a two second improvement in the load time of the Sales Orders (40.100.00) screen.
REFERENCES
For more information about the global assembly cache, click the following article number to view the article in the Microsoft Knowledge Base:
315682 How to install an assembly in the Global Assembly Cache in Visual Basic .NET or in Visual Basic 2005 Additionally, for more information about the global assembly cache, visit the following Microsoft Web site:
http://msdn2.microsoft.com/en-us/library/yf1d93sz(vs.71).aspx
For more information about Native Image Generator, visit the following Microsoft Web site:
http://msdn2.microsoft.com/en-us/library/6t9t5wcf(VS.80).aspx
Windows Article ID : 948496 can be located at the following link:
http://support.microsoft.com/kb/948496/en-us
