This document presents a strategy for converting a Btrieve-based application to a Microsoft SQL Server–based ODBC and SQL application. It outlines a methodology that will allow you to move in two steps from a Btrieve API ISAM-like application to a relational client/server Microsoft SQL Server application. It analyzes different data access and result processing techniques and how they affect the performance of both of these platforms. Using the techniques discussed in this paper, you can create a high performance application that takes full advantage of the power and flexibility of Microsoft SQL Server.
To learn more about developing applications for SQL Server, refer to these sources:
The following tools are available in the Microsoft Windows NT Resource Kit or at the Microsoft Web site:
A Win32® utility that simulates the way SQL Server performs I/O operations with the disk subsystem. It can be used as a diagnostic aid to help determine whether a disk subsystem problem exists.
Used to kill Windows NT processes. Similar to PVIEWER or PVIEW, except it runs from the command prompt and takes a process ID as a parameter.
A Win32 utility to monitor Windows NT processes, memory usage, and so on.
A Windows-based tool that shows the processes running in the system and allows ending processes and boosting priority.
A Windows-based tool that shows the processes running in the system and allows ending processes and boosting priority. Similar to Pview.exe, but allows looking at remote machines.
A tool used to list process names and process IDs running on a system. Use in conjunction with Kill.exe to terminate a process on a remote computer (by using Remote.exe).