Update of /cvsroot/monetdb/sql
In directory 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv11569

Modified Files:
      Tag: Nov2009
        dump-restore.txt dump-restore.html 
Log Message:
Updated dump instructions.

Index: dump-restore.txt
===================================================================
RCS file: /cvsroot/monetdb/sql/dump-restore.txt,v
retrieving revision 1.4
retrieving revision 1.4.16.1
diff -u -d -r1.4 -r1.4.16.1
--- dump-restore.txt    22 Aug 2007 06:22:04 -0000      1.4
+++ dump-restore.txt    6 Nov 2009 09:21:15 -0000       1.4.16.1
@@ -4,19 +4,20 @@
 Start the SQL Server and SQL Client as usual.
 
 In the SQL Client, type the following three commands.  Type them
-without any extra white space:
+at the start of the line::
 
-       >.../dump.sql
+       \>.../dump.sql
        \D
-       >
+       \>
 
-That is, first a line consisting of a greater than symbol followed by
-the absolute (!) path name of the file in which you want to store the
-dump.  This will redirect future output to the file mentioned.  Then a
-line consisting of just backslash-capital D.  This command does the
-actual dump which is, because of the previous line, stored in the dump
-file.  And finally a line with just a greater than symbol.  This
-closes the file and redirects the output again to the screen.
+That is, first a line consisting of a backslash and greater than
+symbol followed by the path name of the file in which you want to
+store the dump.  This will redirect future output to the file
+mentioned.  Then a line consisting of just backslash-capital D.  This
+command does the actual dump which is, because of the previous line,
+stored in the dump file.  And finally a line with a backslash and
+greater than symbol.  This closes the file and redirects the output
+back to the screen.
 
 [Note: if you don't use the absolute path name of a file, the file
 will be created in the directory where the SQL Client was started.  On
@@ -24,9 +25,11 @@
 therefore using an absolute path name is highly recommended.]
 
 It is also possible to dump from the command line.  Start a SQL
-Server, and then issue the command
+Server, and then issue the command::
 
-       msqldump -umonetdb -Pmonetdb > dump.sql
+       msqldump -umonetdb > dump.sql
+
+You will need to provide the password (monetdb).
 
 This command will connect to the SQL Server and dump the database into
 the file dump.sql in the current directory.
@@ -39,14 +42,17 @@
 
 Start the SQL Server and SQL Client as usual.
 
-In the SQL Client, type the following command.
+In the SQL Client, type the following command::
 
-       <.../dump.sql
+       \<.../dump.sql
 
-That is, a less than symbol followed by the absolute (!) path name of
-the dump file that was produced using the dump instructions.
+That is, a backslash and less than symbol followed by the path name of
+the dump file that was produced using the dump instructions.  Again,
+unless you use an absolute path name, the file name is relative to
+where the SQL client was started, which on Windows may not be where
+you expect.
 
 It is also possible to restore from the command line.  Start a SQL
-Server, and then issue the command
+Server, and then issue the command::
 
        mclient -lsql -umonetdb -Pmonetdb < dump.sql

Index: dump-restore.html
===================================================================
RCS file: /cvsroot/monetdb/sql/dump-restore.html,v
retrieving revision 1.10
retrieving revision 1.10.8.1
diff -u -d -r1.10 -r1.10.8.1
--- dump-restore.html   7 Jan 2009 14:19:27 -0000       1.10
+++ dump-restore.html   6 Nov 2009 09:21:15 -0000       1.10.8.1
@@ -21,56 +21,343 @@
 
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
 <html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
-  <head>
-    <title>Dump/Restore of SQL database</title>
-  </head>
-  <body>
-    <h1>
-      <a name="dumping-the-sql-database">Dumping the SQL database.</a>
-    </h1>
-    <p>Start the SQL Server and SQL Client as usual.</p>
-    <p>In the SQL Client, type the following three commands.  Type them
-      without any extra white space:</p>
-    <pre>
-      &gt;.../dump.sql
-      \D
-      &gt;
-    </pre>
-    <p>That is, first a line consisting of a greater than symbol followed by
-      the absolute (!) path name of the file in which you want to store the
-      dump.  This will redirect future output to the file mentioned.  Then a
-      line consisting of just backslash-capital D.  This command does the
-      actual dump which is, because of the previous line, stored in the dump
-      file.  And finally a line with just a greater than symbol.  This
-      closes the file and redirects the output again to the screen.</p>
-    <p>[Note: if you don't use the absolute path name of a file, the file
-      will be created in the dorectory where the SQL Client was started.  On
-      Windows this is at the location where the program was installed, and
-      therefore using an absolute path name is highly recommended.]</p>
-    <p>It is also possible to dump from the command line.  Start a SQL
-      Server, and then issue the command</p>
-    <pre>
-      msqldump -umonetdb -Pmonetdb &gt; dump.sql
-    </pre>
-    <p>This command will connect to the SQL Server and dump the database into
-      the file dump.sql in the current directory.</p>
-    <h1>
-      <a name="restoring-the-sql-database">Restoring the SQL
-      database.</a>
-    </h1>
-    <p>After having dumped the database per the preceding instructions, it is
-      possible to restore the database using the following commands.</p>
-    <p>Start the SQL Server and SQL Client as usual.</p>
-    <p>In the SQL Client, type the following command.</p>
-    <pre>
-      &lt;.../dump.sql
-    </pre>
-    <p>That is, a less than symbol followed by the absolute (!) path name of
-      the dump file that was produced using the dump instructions.</p>
-    <p>It is also possible to restore from the command line.  Start a SQL
-      Server, and then issue the command</p>
-    <pre>
-      mclient -lsql -umonetdb -Pmonetdb &lt; dump.sql
-    </pre>
-  </body>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<meta name="generator" content="Docutils 0.5: 
http://docutils.sourceforge.net/"; />
+<title></title>
+<style type="text/css">
+
+/*
+:Author: David Goodger ([email protected])
+:Id: $Id$
+:Copyright: This stylesheet has been placed in the public domain.
+
+Default cascading style sheet for the HTML output of Docutils.
+
+See http://docutils.sf.net/docs/howto/html-stylesheets.html for how to
+customize this style sheet.
+*/
+
+/* used to remove borders from tables and images */
+.borderless, table.borderless td, table.borderless th {
+  border: 0 }
+
+table.borderless td, table.borderless th {
+  /* Override padding for "table.docutils td" with "! important".
+     The right padding separates the table cells. */
+  padding: 0 0.5em 0 0 ! important }
+
+.first {
+  /* Override more specific margin styles with "! important". */
+  margin-top: 0 ! important }
+
+.last, .with-subtitle {
+  margin-bottom: 0 ! important }
+
+.hidden {
+  display: none }
+
+a.toc-backref {
+  text-decoration: none ;
+  color: black }
+
+blockquote.epigraph {
+  margin: 2em 5em ; }
+
+dl.docutils dd {
+  margin-bottom: 0.5em }
+
+/* Uncomment (and remove this text!) to get bold-faced definition list terms
+dl.docutils dt {
+  font-weight: bold }
+*/
+
+div.abstract {
+  margin: 2em 5em }
+
+div.abstract p.topic-title {
+  font-weight: bold ;
+  text-align: center }
+
+div.admonition, div.attention, div.caution, div.danger, div.error,
+div.hint, div.important, div.note, div.tip, div.warning {
+  margin: 2em ;
+  border: medium outset ;
+  padding: 1em }
+
+div.admonition p.admonition-title, div.hint p.admonition-title,
+div.important p.admonition-title, div.note p.admonition-title,
+div.tip p.admonition-title {
+  font-weight: bold ;
+  font-family: sans-serif }
+
+div.attention p.admonition-title, div.caution p.admonition-title,
+div.danger p.admonition-title, div.error p.admonition-title,
+div.warning p.admonition-title {
+  color: red ;
+  font-weight: bold ;
+  font-family: sans-serif }
+
+/* Uncomment (and remove this text!) to get reduced vertical space in
+   compound paragraphs.
+div.compound .compound-first, div.compound .compound-middle {
+  margin-bottom: 0.5em }
+
+div.compound .compound-last, div.compound .compound-middle {
+  margin-top: 0.5em }
+*/
+
+div.dedication {
+  margin: 2em 5em ;
+  text-align: center ;
+  font-style: italic }
+
+div.dedication p.topic-title {
+  font-weight: bold ;
+  font-style: normal }
+
+div.figure {
+  margin-left: 2em ;
+  margin-right: 2em }
+
+div.footer, div.header {
+  clear: both;
+  font-size: smaller }
+
+div.line-block {
+  display: block ;
+  margin-top: 1em ;
+  margin-bottom: 1em }
+
+div.line-block div.line-block {
+  margin-top: 0 ;
+  margin-bottom: 0 ;
+  margin-left: 1.5em }
+
+div.sidebar {
+  margin: 0 0 0.5em 1em ;
+  border: medium outset ;
+  padding: 1em ;
+  background-color: #ffffee ;
+  width: 40% ;
+  float: right ;
+  clear: right }
+
+div.sidebar p.rubric {
+  font-family: sans-serif ;
+  font-size: medium }
+
+div.system-messages {
+  margin: 5em }
+
+div.system-messages h1 {
+  color: red }
+
+div.system-message {
+  border: medium outset ;
+  padding: 1em }
+
+div.system-message p.system-message-title {
+  color: red ;
+  font-weight: bold }
+
+div.topic {
+  margin: 2em }
+
+h1.section-subtitle, h2.section-subtitle, h3.section-subtitle,
+h4.section-subtitle, h5.section-subtitle, h6.section-subtitle {
+  margin-top: 0.4em }
+
+h1.title {
+  text-align: center }
+
+h2.subtitle {
+  text-align: center }
+
+hr.docutils {
+  width: 75% }
+
+img.align-left {
+  clear: left }
+
+img.align-right {
+  clear: right }
+
+ol.simple, ul.simple {
+  margin-bottom: 1em }
+
+ol.arabic {
+  list-style: decimal }
+
+ol.loweralpha {
+  list-style: lower-alpha }
+
+ol.upperalpha {
+  list-style: upper-alpha }
+
+ol.lowerroman {
+  list-style: lower-roman }
+
+ol.upperroman {
+  list-style: upper-roman }
+
+p.attribution {
+  text-align: right ;
+  margin-left: 50% }
+
+p.caption {
+  font-style: italic }
+
+p.credits {
+  font-style: italic ;
+  font-size: smaller }
+
+p.label {
+  white-space: nowrap }
+
+p.rubric {
+  font-weight: bold ;
+  font-size: larger ;
+  color: maroon ;
+  text-align: center }
+
+p.sidebar-title {
+  font-family: sans-serif ;
+  font-weight: bold ;
+  font-size: larger }
+
+p.sidebar-subtitle {
+  font-family: sans-serif ;
+  font-weight: bold }
+
+p.topic-title {
+  font-weight: bold }
+
+pre.address {
+  margin-bottom: 0 ;
+  margin-top: 0 ;
+  font-family: serif ;
+  font-size: 100% }
+
+pre.literal-block, pre.doctest-block {
+  margin-left: 2em ;
+  margin-right: 2em }
+
+span.classifier {
+  font-family: sans-serif ;
+  font-style: oblique }
+
+span.classifier-delimiter {
+  font-family: sans-serif ;
+  font-weight: bold }
+
+span.interpreted {
+  font-family: sans-serif }
+
+span.option {
+  white-space: nowrap }
+
+span.pre {
+  white-space: pre }
+
+span.problematic {
+  color: red }
+
+span.section-subtitle {
+  /* font-size relative to parent (h1..h6 element) */
+  font-size: 80% }
+
+table.citation {
+  border-left: solid 1px gray;
+  margin-left: 1px }
+
+table.docinfo {
+  margin: 2em 4em }
+
+table.docutils {
+  margin-top: 0.5em ;
+  margin-bottom: 0.5em }
+
+table.footnote {
+  border-left: solid 1px black;
+  margin-left: 1px }
+
+table.docutils td, table.docutils th,
+table.docinfo td, table.docinfo th {
+  padding-left: 0.5em ;
+  padding-right: 0.5em ;
+  vertical-align: top }
+
+table.docutils th.field-name, table.docinfo th.docinfo-name {
+  font-weight: bold ;
+  text-align: left ;
+  white-space: nowrap ;
+  padding-left: 0 }
+
+h1 tt.docutils, h2 tt.docutils, h3 tt.docutils,
+h4 tt.docutils, h5 tt.docutils, h6 tt.docutils {
+  font-size: 100% }
+
+ul.auto-toc {
+  list-style-type: none }
+
+</style>
+</head>
+<body>
+<div class="document">
+
+
+<div class="section" id="dumping-the-sql-database">
+<h1>Dumping the SQL database.</h1>
+<p>Start the SQL Server and SQL Client as usual.</p>
+<p>In the SQL Client, type the following three commands.  Type them
+at the start of the line:</p>
+<pre class="literal-block">
+\&gt;.../dump.sql
+\D
+\&gt;
+</pre>
+<p>That is, first a line consisting of a backslash and greater than
+symbol followed by the path name of the file in which you want to
+store the dump.  This will redirect future output to the file
+mentioned.  Then a line consisting of just backslash-capital D.  This
+command does the actual dump which is, because of the previous line,
+stored in the dump file.  And finally a line with a backslash and
+greater than symbol.  This closes the file and redirects the output
+back to the screen.</p>
+<p>[Note: if you don't use the absolute path name of a file, the file
+will be created in the directory where the SQL Client was started.  On
+Windows this is at the location where the program was installed, and
+therefore using an absolute path name is highly recommended.]</p>
+<p>It is also possible to dump from the command line.  Start a SQL
+Server, and then issue the command:</p>
+<pre class="literal-block">
+msqldump -umonetdb &gt; dump.sql
+</pre>
+<p>You will need to provide the password (monetdb).</p>
+<p>This command will connect to the SQL Server and dump the database into
+the file dump.sql in the current directory.</p>
+</div>
+<div class="section" id="restoring-the-sql-database">
+<h1>Restoring the SQL database.</h1>
+<p>After having dumped the database per the preceding instructions, it is
+possible to restore the database using the following commands.</p>
+<p>Start the SQL Server and SQL Client as usual.</p>
+<p>In the SQL Client, type the following command:</p>
+<pre class="literal-block">
+\&lt;.../dump.sql
+</pre>
+<p>That is, a backslash and less than symbol followed by the path name of
+the dump file that was produced using the dump instructions.  Again,
+unless you use an absolute path name, the file name is relative to
+where the SQL client was started, which on Windows may not be where
+you expect.</p>
+<p>It is also possible to restore from the command line.  Start a SQL
+Server, and then issue the command:</p>
+<pre class="literal-block">
+mclient -lsql -umonetdb -Pmonetdb &lt; dump.sql
+</pre>
+</div>
+</div>
+</body>
 </html>


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Monetdb-sql-checkins mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/monetdb-sql-checkins

Reply via email to