2007/5/16, Franco Guidoli Note the original email was dated way back and it is always good to educate/share experiences. Colin Foss wrote:

I've observed this pattern previously. If the SQL log file grows very large then the server will not respond immediately after a restart. The initial response time can vary from a few seconds to several minutes while the transactions are replayed into the DB. Once the replay is finished the server will respond and the SQL log will shrink to zero for a new session.

In older revisions (last few months) sometimes the server would never respond and I would have to restore from a backup.

The usual way I prevent a non-responsive server restart is to load my tables WITHOUT a primary key. Unique keys will not cause the issue. However, I thought this bug was fixed recently but I haven't verified the fix as my script still use unique keys instead of the formal primary key as I am still loading a lot of data into my own DB.

Hope this helps.

--- Andrei Martsinchyk wrote:

...

Hi Franco,

Guess you did not commit.

Andrei

2007/5/16, Franco Guidoli :

...

Hi all: I'm trying to measure the response time of

...

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

MonetDB against a 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.html...

...

Sent from the monetdb-users mailing list archive at Nabble.com.

---

...

...

This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/monetdb-users

...

---

...

This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005.

http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/> _______________________________________________

...

MonetDB-users mailing list MonetDB-users@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/monetdb-users

------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users