Explore topic-wise InterviewSolutions in .

The triggers are CALLED implicitly by DATABASE generated events, while STORED procedures are called explicitly by client applications.

The triggers are called implicitly by database generated events, while stored procedures are called explicitly by client applications.

The TYPES of transparencies the NOS middleware is expected to provide are:-

• Location transparency
• Namespace transparency
• Logon transparency
• Replication transparency
• Local/Remote ACCESS transparency
• DISTRIBUTED time transparency
• Failure transparency and
• Administration transparency.

The types of transparencies the NOS middleware is expected to provide are:-

There is a many-to-one RELATIONSHIP between clients and server. Clients ALWAYS initiate the DIALOG by requesting a SERVICE. Servers are passively awaiting for REQUESTS from clients.

There is a many-to-one relationship between clients and server. Clients always initiate the dialog by requesting a service. Servers are passively awaiting for requests from clients.

They were originally introduced to run classes of applications that could SERVICE hundreds and sometimes thousands of CLIENTS. TP MONITORS PROVIDE an OS - on top of existing OS - that connects in real time these thousands of humans with a pool of shared server processes.

They were originally introduced to run classes of applications that could service hundreds and sometimes thousands of clients. TP Monitors provide an OS - on top of existing OS - that connects in real time these thousands of humans with a pool of shared server processes.

There is no COMMONLY accepted DEFINITION for a TP MONITOR. According to Jeri EDWARDS' a TP Monitor is "an OS for transaction processing".

There is no commonly accepted definition for a TP monitor. According to Jeri Edwards' a TP Monitor is "an OS for transaction processing".

These are fully-loaded machines which includes MULTIPROCESSORS, high-speed DISK arrays for interview I/O and fault TOLERANT FEATURES.

These are fully-loaded machines which includes multiprocessors, high-speed disk arrays for interview I/O and fault tolerant features.

This new model of Client/Server consists of thin, protable, "universal" clients that talk to superfat SERVERS. In the SIMPLEST form, a WEB server returns documents when clients ask for them by name. The clients and server communicate using an RPC-like protocol called HTTP.

This new model of Client/Server consists of thin, protable, "universal" clients that talk to superfat servers. In the simplest form, a web server returns documents when clients ask for them by name. The clients and server communicate using an RPC-like protocol called HTTP.

TP lite, based on stored PROCEDURES. TP HEAVY, based on the TP MONITORS.

TP lite, based on stored procedures. TP heavy, based on the TP monitors.

TP-Lite is simply the integration of TP MONITOR functions in the DATABASE engines. TP-Heavy are TP Monitors which supports the Client/Server architecture and allow PC to initiate some very COMPLEX multiserver transaction from the DESKTOP.

TP-Lite is simply the integration of TP Monitor functions in the database engines. TP-Heavy are TP Monitors which supports the Client/Server architecture and allow PC to initiate some very complex multiserver transaction from the desktop.

TRANSPARENCY really MEANS HIDING the NETWORK and its servers from the users and even the application programmers.

Transparency really means hiding the network and its servers from the users and even the application programmers.

Triggers are special user defined actions usually in the form of stored procedures, that are automatically invoked by the server BASED on data related events. It can perform complex actions and can USE the full power of procedural LANGUAGES. A rule is a special type of TRIGGER that is USED to perform simple checks on data.

Triggers are special user defined actions usually in the form of stored procedures, that are automatically invoked by the server based on data related events. It can perform complex actions and can use the full power of procedural languages. A rule is a special type of trigger that is used to perform simple checks on data.

• Ubiquitous communications.
• Network OS EXTENSION.
• Binary large objects (BLOBs).
• Global directories and Network YELLOW pages.
• AUTHENTICATION and Authorization services.
• System management.
• Network time.
• Database and transaction services.
• INTERNET services.
• Object- oriented services.

• USER interface
• BUSINESS Logic and
• SHARED DATA.

With a database SERVER, the client passes SQL requests as messages to the database server. The results of each SQL command are returned over the NETWORK. The server USES its own processing power to find the request data instead of passing all the records back to the client and then getting it find its own data. The result is a MUCH more efficient USE of distributed processing power. It is also known as SQL engine.

With a database server, the client passes SQL requests as messages to the database server. The results of each SQL command are returned over the network. The server uses its own processing power to find the request data instead of passing all the records back to the client and then getting it find its own data. The result is a much more efficient use of distributed processing power. It is also known as SQL engine.

With a transaction server, the client INVOKES remote procedures that RESIDE on the server with an SQL database ENGINE. These remote procedures on the server execute a group of SQL statements. The network EXCHANGE consists of a single request/reply message. The SQL statements either all succeed or FAIL as a unit.

With a transaction server, the client invokes remote procedures that reside on the server with an SQL database engine. These remote procedures on the server execute a group of SQL statements. The network exchange consists of a single request/reply message. The SQL statements either all succeed or fail as a unit.

It is a PROTOCOL formerly used to EXCHANGE routing information between Internet core ROUTERS.

It is a protocol formerly used to exchange routing information between Internet core routers.

It is a PROTOCOL used to advertise the SET of networks that can be reached with in an autonomous system. BGP ENABLES this information to be shared with the autonomous system. This is newer than EGP (Exterior Gateway Protocol).

It is a protocol used to advertise the set of networks that can be reached with in an autonomous system. BGP enables this information to be shared with the autonomous system. This is newer than EGP (Exterior Gateway Protocol).

It is a sequence of IP ADDRESSES identifying the route a DATAGRAM MUST follow. A SOURCE route may optionally be included in an IP datagram header.

It is a sequence of IP addresses identifying the route a datagram must follow. A source route may optionally be included in an IP datagram header.

It is a set of rules defining a very SIMPLE VIRTUAL terminal interaction. The NVT is used in the START of a Telnet SESSION.

It is a set of rules defining a very simple virtual terminal interaction. The NVT is used in the start of a Telnet session.

It is a simple PROTOCOL used to EXCHANGE information between the routers.

It is a simple protocol used to exchange information between the routers.

It is a SYSTEM that performs a protocol translation between DIFFERENT electronic MAIL delivery protocols.

It is a system that performs a protocol translation between different electronic mail delivery protocols.

With an object server, the Client/Server application is written as a set of communicating objects. Client object communicate with server objects using an Object REQUEST Broker (ORB). The client INVOKES a method on a remote object. The ORB locates an instance of that object server class, invokes the REQUESTED method and returns the results to the client object. Server objects must provide SUPPORT for concurrency and sharing. The ORB brings it all together.

With an object server, the Client/Server application is written as a set of communicating objects. Client object communicate with server objects using an Object Request Broker (ORB). The client invokes a method on a remote object. The ORB locates an instance of that object server class, invokes the requested method and returns the results to the client object. Server objects must provide support for concurrency and sharing. The ORB brings it all together.