| |
Home |
![[Table of Contents]](/dwicons/b_toc.gif)
|
Introducing Sybase Workplace SQL Server |
![[-]](/dwicons/i_colpse.gif)
| Chapter 1: Overview of Workplace SQL Server |
|
| Components of Workplace SQL Server |
As the section "Client/Server Architecture", described, the basic client/server RDBMS model consists of the database server and third-party or developed client software that communicates with the database server over a network. The integrated set of products in Workplace SQL Server also includes software for backing up, monitoring, and administering SQL Server as well as client libraries that enable applications to communicate with the server.
You install some of the Workplace SQL Server software on the server and some on the client.
In addition, to prepare the server, you dedicate raw partitions for use as database devices, disk partitions dedicated to storing data before installing SQL Server. After installation you use the Transact-SQL disk init command to initialize the device.
On the client you will most likely install (in addition to the client components of SQL Server) development tools such as PowerBuilder that help you build applications that access SQL Server, the applications themselves, and/or third-party software.
Figure 1-7 shows an overview of the client and server components of your SQL Server system. The sections "Server Components" and "Client Components" describe each of the components in more detail.
Figure 1-7: Overview of Workplace SQL Server components
The following Workplace SQL Server components reside on the server:
SQL Server is Sybase's high-performance RDBMS. You can get a technical overview of SQL Server release 11.0.x from the product description and the white papers accessible from the Sybase home page on the World Wide Web at the following address:
http://www.sybase.com
Also ask your sales representative for more information. There are also several excellent books about SQL Server available from Sybase Press as well as from third-party publishers.
SQL Server also includes several utilities, which are described in SQL Server Utilities Programs for your platform.
Backup Server is a server application that runs concurrently with SQL Server to perform high-speed on-line database dumps and loads. Backup Server is automatically installed when you install SQL Server.
Monitor Server and Monitor Historical Server are the server components of a client/server application called SQL Server Monitor Server, which allows you to capture, display, and evaluate SQL Server performance data and to tune SQL Server performance. Monitor Server captures performance data from SQL Server's shared memory; Monitor Historical Server writes the data to files for off-line analysis. You must install Monitor Server on the same machine as the SQL Server that you want to monitor. Monitor Historical Server performs best when installed on a different machine from the SQL Server being monitored.
The following Workplace SQL Server components are client components:
SQL Server Manager is a graphical system administration and database administration tool for SQL Server. Its powerful collection of features make exacting administrative tasks easy to perform. Figure 1-8 shows the SQL Server Manager user interface.
Figure 1-8: The SQL Server Manager user interface
SQL Server Manager helps with the following typical system or database administrator's tasks:
This client application gathers data collected by Monitor Server and presents it to the user through a graphical user interface. Monitor Client makes it easy to view SQL Server performance data and tune SQL Server performance parameters. Monitor Client also includes Monitor Client Library, which provides a programmatic interface to Monitor Server.
Open Client contains APIs that enable client applications to interface with SQL Server. These APIs are Client-Library(TM), DB-Library(TM), and CS-Library. Client applications that you purchase or develop, as well as application development tools such as PowerBuilder(R) and Infomaker, require that these Open Client libraries be installed so that they can communicate with SQL Server.
CS-Library contains a collection of utility routines used by all client applications. Client-Library and DB-Library contain a collection of routines that are specific to the programming language being used in an application. Client-Library is an extension of the older DB-Library that accommodates new features supported by SQL Server release 10 and later; DB-Library supports pre-system 10 features. For more information, consult the documentation in the Open Client/Server(TM) collection of SyBooks(TM) (see "Sybase Documentation").
Open Client includes Net-Library(TM), a library containing network protocol services that support connections between client applications and SQL Server.
Open Client also includes the following utilities:
You install Open Client on all machines that will run client software that accesses SQL Server.
Icons for frequently used client utilities appear on the desktop. These include:
ODBC is the API developed by Microsoft to allow clients to connect to heterogeneous RDBMSs.
You will install and use the appropriate ODBC driver, which resides on the client, only if you are developing or running third-party client applications that require access to SQL Server through Microsoft's ODBC interface. You install the ODBC drivers from the floppy disks included in the box.
|
|