Is there any method, besides restarting the database,
of shrinking the sql log file?
When I am performing a large set of large inserts (via
COPY INTO) the log file gets very large. I wish there
was a way to cycle the log file.
Also during these large batches of inserts the
database server becomes less and less responsive until
I am forced to restart the server. Upon restart and
the normal recovery monet returns to a very responsive state.
Hi all: I'm trying to measure the response time of MonetDB against a
commercial RDBMS, so I've made a dump of the data from my current database
in order to load into MonetDB. I have approximately 2.6 million rows,
divided into 26 flat files of 100k rows each one, which I load using then
SQL command "copy into....". Everything works ok with the data load
(performing a commit after each 100k file), and I can make use of that data
in the same session from which I've loaded the data, but when I restart
MonetDB Server, I can't login via SQL (I can start MonetDB Server, but SQL
Client doesn't respond).
Apparently, from what I can realize, after the shutdown of MonetDB Server,
there is a big log file in Monet's sql_logs directory, and when I get a
response from SQL Client, the log file is apparently empty (I've realized
this loading only 200k rows).
Is this the expected behaviour for the MonetDB SQL Server? Did I miss
anything in order to avoid this? After the second start of the server, this
doesn't happen anymore until I load new data.
I'm working with MonetDB Server v5.0.0_beta1_2 (downloaded msi from
sourceforge) over Windows XP, and the SQL Client is via JDBC.
Thanks in advance for any help you can give me.
Franco
--
View this message in context: http://www.nabble.com/Not-responding-after-sql-server-restart-tf3762198.htm…
Sent from the monetdb-users mailing list archive at Nabble.com.
Hi,
I know Monetdb works with aqua studio,sql view. But if you are working with
eclipse it is nice to have a plugin that talks to monetdb. I have just came
across http://eclipsesql.sourceforge.net/. It looks really nice and is jdbc
compliant. There is a standalone version as well if you dont use eclipse.
Thanks
Bharani
--
View this message in context: http://www.nabble.com/SQL-Explorer---SQL-Frontend-for-MonetDB-SQL-tf4168853…
Sent from the monetdb-users mailing list archive at Nabble.com.
Hi,
I am trying to test the backup/restore of a MonetDB database. I
installed MonetDB latest version on a 32Bit Red hat Linux. I created a
database on Machine-1, created a table and loaded the table with 1M
rows. After that I shutdown the database and took a back-up of the
entire "dbfarm" directory. I moved the backup to Machine-2 where the
"dbfarm" directory points to the similar location as Machine-1. I then
opened the database on Machine-2 but there is no table/data on
Machine2 even though the directory contents between the 2 machines
appear the same. Please let me know if I am missing something.
I also made sure that Machine-2 is not creating the database in any
other location, except the location where I copied all the files.
The idea here is to create the database on one machine and then move
the database to different machine using simple file system COPY.
Thanks,
- Venks
Hello! I am bored today. I am nice girl that would like to chat with you. Email me at onauz(a)imailmessage.info only, because I am writing not from my personal email. Wanna see some pictures of me?
Hi all,
I'd like to bring a little program to your attention that may or may not
be useful to you: merovingian.
Merovingian is meant as end-user program to start and stop one or more
MonetDB databases. The program allows itself to be naturally used into
start and stop scripts, as well as manual use from the console. It is
aimed at MonetDB5/SQL users.
In short, merovingian performs two basic tasks:
1. handle connections from clients and redirect those connections to
the appropriate mserver process, and
2. start an mserver process in case it is not running (any more).
Currently, an appropriate mserver process is defined by the database a
client requests for. Since each mserver process only serves one
database, multiple mserver processes are necessary to deal with multiple
databases.
Because merovingian can start mserver processes on demand, it has the
potential to (attempt to) restart an mserver after it has crashed.
Since merovingian will (currently only) start mserver processes, output
of those processes might get confusing, especially when multiple servers
are started. Also, interacting with them is non-trivial. For this
reason, merovingian starts mserver processes as daemon processes in the
background and catches their outputs to display it in a log-like
fashion. Distinction is made between messages and errors. Not
surprisingly both outputs can be written to a logfile on disk or just
outputted to the console. An example output on the console would look
like this:
% merovingian demo
MSG merovingian[30160]: Merovingian 0.3 starting ...
MSG mserver5[30162]: executing 'bin/mserver5' for database 'demo'
MSG merovingian[30160]: monitoring dbfarm var/MonetDB5/dbfarm
MSG merovingian[30160]: listening for connections on pegasus.ins.cwi.nl:50000
MSG merovingian[30160]: starting database 'demo'
ERR mserver5[30162]: #warning: please don't forget to set your vault key!
ERR mserver5[30162]: #(see etc/monetdb5.conf)
MSG mserver5[30162]: # MonetDB server v5.1.0, based on kernel v1.19.0
MSG mserver5[30162]: # Serving database 'demo'
MSG mserver5[30162]: # Compiled for x86_64-pc-linux-gnu/64bit with 64bit OIDs dynamically linked
MSG mserver5[30162]: # Copyright (c) 1993-2007 CWI, all rights reserved
MSG mserver5[30162]: # Visit http://monetdb.cwi.nl/ for further information
MSG mserver5[30162]: # Listening for connection requests on mapi:monetdb://127.0.0.1:50001/
In this example merovingian was requested to start database demo
upfront, without waiting for a client to ask for it. Without the demo
argument, merovingian waits for connections that ask for a database and
starts it at that time. An arbitrary number of databases can be given
as "pre-start" arguments. Pre-starting databases can be important when
clients are used that do not request for a specific database. In such
case, the client is redirected to the first database that is running at
that moment.
Please look at the Merovingian section in the etc/monetdb5.conf file for
more options for merovingian. The section is still small, but it might
grow.
Merovingian is available in the development branch (CVS head) of the
MonetDB5 repository. Feedback is welcome.