1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
|
<HTML>
<HEAD>
<TITLE></TITLE>
<LINK REL="ToC" HREF="httoc.htm">
<LINK REL="Index" HREF="htindex.htm">
<LINK REL="Next" HREF="td000004.htm">
<LINK REL="Previous" HREF="td000002.htm"></HEAD>
<BODY BGCOLOR="#FFFFFF">
<P ALIGN=CENTER>
<A HREF="td000002.htm" TARGET="_self"><IMG SRC="gtd/graprev.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Previous Page"></A>
<A HREF="httoc.htm" TARGET="_self"><IMG SRC="gtd/gratoc.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="TOC"></A>
<A HREF="htindex.htm" TARGET="_self"><IMG SRC="gtd/graindex.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Index"></A>
<A HREF="td000004.htm" TARGET="_self"><IMG SRC="gtd/granext.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Next Page"></A>
<A NAME="E9E2"></A>
<H1>
<FONT FACE="Arial"><B>SOLID </B><B>HAS THE S</B><B>OLUTION</B></FONT></H1>
<BR>
<BLOCKQUOTE>
<P>SOLID <I>Server</I> provides robust transaction processing power combined with cost-effective distribution in high volumes. The following chapters introduce the unique features that make SOLID <I>Server</I> the right data management solution for modern applications.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>
<IMG SRC="gtd/td000005.gif" WIDTH = 265 HEIGHT = 255 ALT="Undisplayed Graphic">
</BLOCKQUOTE>
<BLOCKQUOTE>
<P><I>SOLID Server provides a unique combination of robust transaction processing power and </I><I>cost-effective distribution in high volumes. Load a free evaluation copy from SOLID Online </I><I>Services: </I><B>http://www.solidtech.com</B>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>With legacy technology, features and power are achieved by compromising care-free and compact design; those products cannot be embedded in high-volume applications.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>Simple database packages developed for PCs and small LANs may be compact and easy to deploy, but they do not provide the scalability, performance, and robustness needed for mission-critical applications.
</BLOCKQUOTE>
<A NAME="E10E6"></A>
<H2>
<FONT FACE="Arial"><B>High Volume Component</B></FONT></H2>
<H3>
<FONT FACE="Arial"><A NAME="I2"></A><A NAME="I3"></A><A NAME="I4"></A><A NAME="I5"></A><A NAME="I6"></A><A NAME="I7"></A><A NAME="I8"></A><A NAME="I9"></A><A NAME="I10"></A><A NAME="I11"></A><A NAME="I12"></A><A NAME="I13"></A><A NAME="I14"></A><A NAME="I15"></A><A NAME="I16"></A><A NAME="I17"></A><A NAME="I18"></A><A NAME="I19"></A><A NAME="I20"></A><A NAME="I21"></A><A NAME="I22"></A><A NAME="I23"></A><A NAME="I24"></A><A NAME="I25"></A><A NAME="I26"></A><B>Cost-effective Deployment</B><A NAME="I27"></A><A NAME="I28"></A></FONT></H3>
<TABLE >
<TR>
<TD WIDTH=144 VALIGN=top >
<P>
<IMG SRC="gtd/td000006.gif" WIDTH = 68 HEIGHT = 70 ALT="Undisplayed Graphic">
</TD><TD WIDTH=432 VALIGN=top >
<BLOCKQUOTE>
<P>Installation of SOLID <I>Server</I> typically takes just a few minutes. No special skills are needed, just a simple installation program and two or three diskettes. SOLID <I>Server</I> can be deployed easily also through Internet connections. It is easily embedded into application packages and provides advanced licensing options.</TD></TR></BLOCKQUOTE></TABLE><H3>
<FONT FACE="Arial"><B>Ease of Use</B></FONT></H3>
<BLOCKQUOTE>
<P>In modern decentralized and mobile solutions, the database server's ease of use is increasingly important. SOLID <I>Server</I> runs continuously and automatically performs all administrative tasks such as backup and checkpoint creation. Naturally, SOLID <I>Server</I> recovers automatically from system failures.
</BLOCKQUOTE>
<H3>
<FONT FACE="Arial"><A NAME="I29"></A><A NAME="I30"></A><A NAME="I31"></A><A NAME="I32"></A><A NAME="I33"></A><A NAME="I34"></A><A NAME="I35"></A><A NAME="I36"></A><A NAME="I37"></A><A NAME="I38"></A><A NAME="I39"></A><A NAME="I40"></A><A NAME="I41"></A><A NAME="I42"></A><A NAME="I43"></A><A NAME="I44"></A><A NAME="I45"></A><A NAME="I46"></A><A NAME="I47"></A><A NAME="I48"></A><A NAME="I49"></A><A NAME="I50"></A><A NAME="I51"></A><A NAME="I52"></A><A NAME="I53"></A><B>Reduced Administration Costs</B></FONT></H3>
<BLOCKQUOTE>
<P>In a typical client/server configuration, the long-term costs are mainly personnel costs. Gartner Group estimates that personnel costs, such as administration and end-user support, account for as much as 85% of the 5-year costs of a project deploying client/server technology. SOLID <I>Server</I> is specifically designed to reduce these costs.<A NAME="I54"></A><A NAME="I55"></A> No heavily trained database administrators are needed.
</BLOCKQUOTE>
<H3>
<FONT FACE="Arial"><A NAME="I56"></A><A NAME="I57"></A><A NAME="I58"></A><A NAME="I59"></A><A NAME="I60"></A><A NAME="I61"></A><A NAME="I62"></A><A NAME="I63"></A><A NAME="I64"></A><A NAME="I65"></A><A NAME="I66"></A><A NAME="I67"></A><A NAME="I68"></A><A NAME="I69"></A><A NAME="I70"></A><A NAME="I71"></A><A NAME="I72"></A><A NAME="I73"></A><A NAME="I74"></A><A NAME="I75"></A><A NAME="I76"></A><A NAME="I77"></A><A NAME="I78"></A><A NAME="I79"></A><A NAME="I80"></A><A NAME="I81"></A><A NAME="I82"></A><A NAME="I83"></A><A NAME="I84"></A><A NAME="I85"></A><B>Small Footprint and Scalability</B></FONT></H3>
<BLOCKQUOTE>
<P>The central memory and disk space requirements for SOLID <I>Server</I> are very modest. It runs on hardware from small mobile devices to heavy-weight multiprocessing environments.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>Most databases get slow as they grow. With SOLID <I>Server</I>, active new data is separated from older, more stable data. The small active index — the unique Bonsai Tree<SUP>TM</SUP> — stores new data in the central memory. More stable data is maintained in the storage server. The fast and efficient Bonsai Tree provides conflict detection and a consistent view of data and ensures optimal performance also with very large databases.
</BLOCKQUOTE>
<H3>
<FONT FACE="Arial"><A NAME="I86"></A><A NAME="I87"></A><A NAME="I88"></A><A NAME="I89"></A><A NAME="I90"></A><A NAME="I91"></A><A NAME="I92"></A><A NAME="I93"></A><A NAME="I94"></A><A NAME="I95"></A><A NAME="I96"></A><A NAME="I97"></A><A NAME="I98"></A><A NAME="I99"></A><B>Reduced Hardware Costs</B></FONT></H3>
<BLOCKQUOTE>
<P>In a smaller system, no dedicated database server is needed. But no matter how large a system is built, SOLID <I>Server</I> stays lean and mean. It needs less hardware than comparable databases to provide similar performance.
</BLOCKQUOTE>
<A NAME="E10E7"></A>
<H2>
<FONT FACE="Arial"><B>Open Component</B></FONT></H2>
<BLOCKQUOTE>
<P>SOLID <I>Server</I>
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>operates on all major hardware and operating system platforms
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>makes database files binary compatible between different hardware and operating system environments
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>supports all major communication protocols
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>supports multiple communication protocols simultaneously
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>offers a uniform SQL API on all supported platforms
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>offers the same features and functionality in all environments
</BLOCKQUOTE></UL>
<H3>
<FONT FACE="Arial"><A NAME="I100"></A><A NAME="I101"></A><A NAME="I102"></A><A NAME="I103"></A><A NAME="I104"></A><A NAME="I105"></A><A NAME="I106"></A><A NAME="I107"></A><A NAME="I108"></A><A NAME="I109"></A><A NAME="I110"></A><A NAME="I111"></A><A NAME="I112"></A><A NAME="I113"></A><B>Portability</B></FONT></H3>
<BLOCKQUOTE>
<P>SOLID <I>Server</I> is designed for optimum portability<A NAME="I114"></A><A NAME="I115"></A>. It supports all major operating systems, networks, and communication protocols and stores the data in the same binary format across platforms. A uniform SQL API facilitates the development of portable client applications. These features together enable you to easily provide multi-platform solutions.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>Migrating from one operating environment to another is the easiest in the DBMS market: database files are binary compatible between operating system environments. This means that a database created and used, for example, in a single-user Windows environment can be copied directly into any other supported environment, where it can be used immediately by the corresponding SOLID <I>Server </I>process.
</BLOCKQUOTE>
<H3>
<FONT FACE="Arial"><A NAME="I116"></A><A NAME="I117"></A><A NAME="I118"></A><A NAME="I119"></A><A NAME="I120"></A><A NAME="I121"></A><A NAME="I122"></A><A NAME="I123"></A><A NAME="I124"></A><A NAME="I125"></A><A NAME="I126"></A><A NAME="I127"></A><A NAME="I128"></A><A NAME="I129"></A><B>Standards</B></FONT></H3>
<TABLE >
<TR>
<TD WIDTH=144 VALIGN=top >
<P>
<IMG SRC="gtd/td000007.gif" WIDTH = 112 HEIGHT = 112 ALT="Undisplayed Graphic">
</TD><TD WIDTH=432 VALIGN=top >
<BLOCKQUOTE>
<P>Information technology is changing so fast that today's system — no matter how advanced — can be tomorrow's dinosaur. The best way to protect a software investment is to invest in a standard system. SOLID <I>Server</I> is designed in compliance with all relevant SQL standards: ANSI SQL2, Microsoft ODBC, and SQL Access Group CLI. Strict adherence to standards means that our partners are not tied to any particular hardware, development tools, or system software.</TD></TR></BLOCKQUOTE></TABLE><BLOCKQUOTE>
<P>The bottom line is that if you are satisfied with SOLID <I>Server</I>, you can expand the system as needed. If for some reason SOLID <I>Server</I> does not meet your expectations, you are free to adopt another DBMS solution without sacrificing your investments in applications or in IT infrastructure.
</BLOCKQUOTE>
<A NAME="E10E8"></A>
<H2>
<FONT FACE="Arial"><B>Industrial Strength Component</B></FONT></H2>
<BLOCKQUOTE>
<P>SOLID <I>Server</I> is powerful and complete. It provides the robustness and functionality that professionals expect to find in an industrial-strength database server.
</BLOCKQUOTE>
<H3>
<FONT FACE="Arial"><A NAME="I130"></A><A NAME="I131"></A><A NAME="I132"></A><A NAME="I133"></A><A NAME="I134"></A><A NAME="I135"></A><A NAME="I136"></A><A NAME="I137"></A><A NAME="I138"></A><A NAME="I139"></A><A NAME="I140"></A><A NAME="I141"></A><A NAME="I142"></A><A NAME="I143"></A><A NAME="I144"></A><A NAME="I145"></A><A NAME="I146"></A><B>Reliability</B></FONT></H3>
<BLOCKQUOTE>
<P>The reliability of a database is typically its most valued characteristic. The modern client/server database server should provide the same level of security and integrity that mainframes traditionally offered. The reliability features of SOLID <I>Server</I> include:<A NAME="I147"></A><A NAME="I148"></A>
</BLOCKQUOTE>
<UL>
<BLOCKQUOTE>
<LI>Online administration
<BR>All administrative operations, including creation of backups and checkpoints, can be performed either automatically or at the administrator's request, concurrently with normal database use.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Timed commands
<BR>SOLID <I>Server</I> has a built-in timer that can be used for various administrative tasks. Typically the timer is used for automating backups to be run daily or weekly, but it can also be used to run various other commands.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Adjacent operation and transaction logs
<BR>For efficient recovery from possible error situations, SOLID <I>Server</I> provides full logging of committed database operations. It is thus able to recover from a system failure with its data integrity intact.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Fast and automatic roll-forward recovery
<BR>In the case of a system malfunction, such as a power failure, SOLID <I>Server</I> automatically performs a roll-forward recovery. This means that the database is returned to the state it was in at the moment of the error situation. To guarantee database integrity, all committed transactions are read from the transaction log.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI>Centralized administration
<BR>With SOLID <I>Remote Control</I>, it is easy to administer multiple distributed servers running on heterogeneous platforms from a single workstation.
</BLOCKQUOTE>
<BLOCKQUOTE>
<LI><A NAME="I149"></A><A NAME="I150"></A><A NAME="I151"></A><A NAME="I152"></A><A NAME="I153"></A><A NAME="I154"></A><A NAME="I155"></A><A NAME="I156"></A>Access rights
<BR>In addition to user-based privileges, SOLID <I>Server</I> offers the convenience of role-based administration. Users can be added to more than one role, and privileges can be granted or revoked at the role level as needed.
</BLOCKQUOTE></UL>
<H3>
<FONT FACE="Arial"><A NAME="I157"></A><A NAME="I158"></A><A NAME="I159"></A><A NAME="I160"></A><A NAME="I161"></A><A NAME="I162"></A><A NAME="I163"></A><A NAME="I164"></A><A NAME="I165"></A><A NAME="I166"></A><A NAME="I167"></A><A NAME="I168"></A><A NAME="I169"></A><A NAME="I170"></A><A NAME="I171"></A><A NAME="I172"></A><A NAME="I173"></A><B>Scalability</B></FONT></H3>
<BLOCKQUOTE>
<P>Scalability is one of the cornerstones SOLID <I>Server</I> was designed and built on. SOLID <I>Server</I> offers the same database technology and the same ease of use on a wide variety of platforms ranging small mobile devices to heavy-weight multiprocessing environments.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>SOLID <I>Server</I> is the first product in the RDBMS market to provide an efficient solution for all of the following application environments<A NAME="I174"></A><A NAME="I175"></A>:
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>
<FONT FACE="Arial"><B>Personal Databases </B><A NAME="I176"></A></FONT>
</BLOCKQUOTE>
<TABLE >
<TR>
<TD WIDTH=144 ALIGN=center VALIGN=top >
<P>
<IMG SRC="gtd/td000008.gif" WIDTH = 76 HEIGHT = 71 ALT="Undisplayed Graphic">
</TD><TD WIDTH=432 VALIGN=top >
<BLOCKQUOTE>
<P>SOLID <I>Server</I> has extraordinarily modest minimum hardware requirements. The small footprint enables SOLID <I>Server</I> to be embedded easily into personal and mobile solutions. All the features of SOLID <I>Server</I> including full SQL standards conformance, advanced transaction management, and recovery are also available in desktop or mobile device environments.</TD></TR></BLOCKQUOTE></TABLE>
<BLOCKQUOTE>
<P>
<FONT FACE="Arial"><B>Workgroup Servers </B><A NAME="I177"></A></FONT>
</BLOCKQUOTE>
<TABLE >
<TR>
<TD WIDTH=144 ALIGN=center VALIGN=top >
<P>
<IMG SRC="gtd/td000009.gif" WIDTH = 90 HEIGHT = 118 ALT="Undisplayed Graphic">
</TD><TD WIDTH=432 VALIGN=top >
<BLOCKQUOTE>
<P>In workgroup server configurations, SOLID <I>Server</I> can be used in various Intel-based operating environments.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>Due to efficient loading and indexing operations, SOLID <I>Server</I> is also well suited for decision-support systems, where large amounts of data are repeatedly moved from the enterprise server to a local server for further analysis.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>Furthermore, SOLID <I>Server’s</I> ease of use is an important consideration for workgroup database servers. More and more workgroup applications are running in LAN environments where usually no trained database administration personnel is available.</TD>
</TR>
</BLOCKQUOTE>
<TR>
<TD WIDTH=144 ALIGN=center VALIGN=top >
<P>
<IMG SRC="gtd/td000010.gif" WIDTH = 87 HEIGHT = 210 ALT="Undisplayed Graphic">
</TD><TD WIDTH=432 VALIGN=top >
<BLOCKQUOTE>
<P>
<FONT FACE="Arial"><B>Enterprise-wide Solutions</B></FONT>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>SOLID <I>Server</I> is an industrial-strength DBMS allowing scalability all the way to powerful multiprocessor platforms. There are no limits to the number of tables, attributes, rows, keys, or key parts. SOLID <I>Server</I> supports variable length data and BLObs up to 2 GB. The maximum database size is over 30 TB. The SOLID product suite also includes tools for integrating mobile computing into corporate information technology using the three-tier client/server architecture paradigm. Additionally, SOLID <I>Server</I> is well suited for implementing Internet and intranet solutions.</TD></TR></BLOCKQUOTE></TABLE>
<H3>
<FONT FACE="Arial"><A NAME="I178"></A><A NAME="I179"></A><A NAME="I180"></A><A NAME="I181"></A><A NAME="I182"></A><A NAME="I183"></A><A NAME="I184"></A><A NAME="I185"></A><A NAME="I186"></A><A NAME="I187"></A><A NAME="I188"></A><A NAME="I189"></A><A NAME="I190"></A><A NAME="I191"></A><A NAME="I192"></A><A NAME="I193"></A><A NAME="I194"></A><A NAME="I195"></A><A NAME="I196"></A><A NAME="I197"></A><A NAME="I198"></A><A NAME="I199"></A><A NAME="I200"></A><A NAME="I201"></A><A NAME="I202"></A><B>Unique Transaction Management Power</B></FONT></H3>
<BLOCKQUOTE>
<P>
<FONT FACE="Arial"><B>Optimistic Concurrency Control</B></FONT>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>SOLID <I>Server</I> separates active data from older, more stable data. The small active index — the unique Bonsai Tree — stores new data by maintaining multiversion information with time dimensions. More stable data is stored in the storage server.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>Because of the time dimension of the Bonsai Tree, each transaction has its own consistent view of the database — this makes locking unnecessary. When the transaction commits, SOLID <I>Server</I> checks that no conflicting operations were made to the small and efficient main memory Bonsai Tree by simultaneous transactions.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>
<FONT FACE="Arial"><B>Row-level Locking</B></FONT>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>However, there are situations when pessimistic concurrency control (locking) is more appropriate. For example, in some applications there are small areas that are very frequently updated. In the case of these so-called ‘hot spots’, conflicts are so probable that optimistic concurrency control wastes effort in rolling back conflicting transactions.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>
<FONT FACE="Arial"><B>The Unique Combination</B></FONT>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>SOLID <I>Server </I>provides a unique combination of traditional row-level locking and advanced optimistic concurrency control. Row-level locking can be turned on table by table, and a single transaction can use both concurrency control methods simultaneously. All this functionality, supported for both read-only and read-write transactions, can be used within the ANSI standard SQL syntax without any proprietary extensions.
<BR>
</BLOCKQUOTE>
<TABLE >
<TR>
<TD WIDTH=149 VALIGN=top >
<P>
<IMG SRC="gtd/td000011.gif" WIDTH = 145 HEIGHT = 154 ALT="Undisplayed Graphic">
</TD><TD WIDTH=303 VALIGN=top >
<BLOCKQUOTE>
<P><I>The unique </I>SOLID<I> Bonsai Tree offers optimistic </I><I>multiversion concurrency control It never causes </I><I>operations to wait for locks. It offers better performance for </I><I>the majority of applications. No effort is wasted in </I><I>maintaining locks and in deadlock resolution algorithms.</I></TD></TR></BLOCKQUOTE></TABLE>
<H3>
<FONT FACE="Arial"><A NAME="I203"></A><A NAME="I204"></A><A NAME="I205"></A><A NAME="I206"></A><A NAME="I207"></A><A NAME="I208"></A><A NAME="I209"></A><A NAME="I210"></A><A NAME="I211"></A><A NAME="I212"></A><A NAME="I213"></A><A NAME="I214"></A><A NAME="I215"></A><A NAME="I216"></A><A NAME="I217"></A><A NAME="I218"></A><A NAME="I219"></A><A NAME="I220"></A><A NAME="I221"></A><A NAME="I222"></A><A NAME="I223"></A><A NAME="I224"></A><A NAME="I225"></A><A NAME="I226"></A><A NAME="I227"></A><B>Synchronization</B></FONT></H3>
<BLOCKQUOTE>
<P>For mobile and distributed solutions, SOLID <I>Synchronizer </I>addresses the major issues related to bi-directional data synchronization. It is based on a few concepts that maintain the simplicity, robustness, and performance of the overall business system.
</BLOCKQUOTE>
<TABLE >
<TR>
<TD WIDTH=144 VALIGN=top >
<P>
<IMG SRC="gtd/td000012.gif" WIDTH = 128 HEIGHT = 483 ALT="Undisplayed Graphic">
</TD><TD WIDTH=456 VALIGN=top >
<BLOCKQUOTE>
<P>
<FONT FACE="Arial"><B>Master and Replica Databases</B></FONT>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>The master database always contains the official version of the data. For each data item, i.e., row of a table, there can be only one master version. All other versions of the same data are replicas.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>The replica database is a subset or a full set of the master database. It contains a tentative version of the data. In addition to the data, it contains transactions that need to be committed later in the master database.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>
<FONT FACE="Arial"><B>Database Synchronization</B></FONT>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>Database synchronization is a process after which the contents of the master and replica databases are equal. The synchronization process is always carried out between two databases of which one acts as a master database and the other as a replica database. The synchronization process contains two major parts: data replication and transaction propagation.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>
<FONT FACE="Arial"><B>Publications and Subscriptions</B></FONT>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>A <I>publication</I> is a subset of the master database that propagates out to replicas. Replica databases use <I>subscriptions</I> to request publications. After the replica database has received the initial <I>full publication</I>, only <I>publication updates</I> that contain the latest modifications need to be sent to the replica.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>
<FONT FACE="Arial"><B>Intelligent Transactions</B></FONT>
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>In real-life business applications, the business logic is vital for proper conflict detection in data synchronization. Only in the most simple applications just transferring the data is adequate.
</BLOCKQUOTE>
<BLOCKQUOTE>
<P>In order to address this problem and avoid the issues that arise from the trigger based conflict resolution approach, Solid introduces a concept of <I>intelligent transactions.</I> An intelligent transaction contains not only the transaction itself, but also the validation and error handling logic that is needed to ensure master data validity and integrity.</TD></TR></BLOCKQUOTE></TABLE>
<A NAME="E7E4"></A>
<P ALIGN=CENTER>
<A HREF="td000002.htm" TARGET="_self"><IMG SRC="gtd/graprev.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Previous Page"></A>
<A HREF="httoc.htm" TARGET="_self"><IMG SRC="gtd/gratoc.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="TOC"></A>
<A HREF="htindex.htm" TARGET="_self"><IMG SRC="gtd/graindex.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Index"></A>
<A HREF="td000004.htm" TARGET="_self"><IMG SRC="gtd/granext.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Next Page"></A>
<center><p><font SIZE=-2>Copyright © 1992-1997 Solid Information Technology Ltd All rights reserved.</font></p></center>
</BODY></HTML>
|
