SQL SERVER Network Protocols and Pagefile and PeopleSoft Application Recommendation

SQL Server 2005 supports the following network protocols:

• Named Pipes
• Virtual Interface Adapter (VIA)
• Shared Memory

Configuring the correct network protocol is critical from a performance and stability perspective. The following section discusses recommendations for configuring network protocols for PeopleSoft applications.

For TCP/IP, data transmissions are more streamlined and have less overhead than Named Pipes. Data transmissions can also take advantage of TCP/IP Sockets performance enhancement mechanisms, such as windowing, delayed acknowledgements, and so on. This can be very helpful in high network traffic scenarios. For PeopleSoft applications, such performance differences can be significant. For best performance, install TCP/IP on the server and configure SQL Server TCP/IP to communicate with clients.

The Named Pipes network protocol can be used only when the application server or process scheduler is running on the same physical computer as the database engine. For the application to use Named Pipes as the first choice network protocol, make sure that in the Client Configuration section of SQL Server Configuration Manager that Named Pipes has a higher order than TCP/IP. Ensure that SQL Server uses Named Pipes in addition to TCP/IP. For this to work, you must also configure native ODBC connections to use Named Pipes.

The VIA (Virtual Interface Adapter) protocol works only with specialized VIA hardware. If you are using VIA hardware, enable this protocol. If you do not have VIA hardware, keep this protocol disabled. The default is disabled.
Shared Memory is a non-routable protocol and is not useful for PeopleSoft applications.

SQL Native Client
SQL Server 2005 introduces a new data access technology called SQL Native Client (SNAC). SQL Native Client contains the SQL OLE DB provider and SQL ODBC driver in one native dynamic link library (DLL) supporting applications using native code APIs (ODBC, OLE DB, and ADO) to Microsoft SQL Server. It is recommended to use the SQL Native Client rather than MDAC for data access to SQL Server 2005 for PeopleSoft applications.

SQL Native Client provides access to new features of SQL Server and also provides full backward compatibility to ODBC and OLE DB.

For PeopleSoft applications, SQL Native Client provides access to new features such as database mirroring and also provides some performance optimizations.

To configure SQL Native Client, navigate to the ODBC Data Source Administrator in the Control Panel. Select SQL Native Client as the new data source driver and configure the data source.