I am interested to hear what your experience is about putting the the <database>.log file on another disk (controller) as is good practice?

I am also wondering what it means for compatibility when transferring the (two) database files between Windows and macOS. As the path to the <database>.log file is somewhere stored in the <database>.db file (I assume), is it stored in Windows and Unix/macOS form and therefor still the same convenience as if they are both at the same location.

By the way, I like to say that for our company, this feature of being able to transfer the database files between various operating systems is just outstanding! One big practical advantage compared to other databases.

Regards, Robert

asked 17 Jan, 04:07

robert's gravatar image

accept rate: 0%

edited 17 Jan, 04:09

It depends how often the data is modified in the DB. If your log file doesn't grow fast, maybe it is not worth separating DB and LOG files. I/O analysis is important. This isn't the actual answer, just a comment, but I'd better test different scenarios on your environment before suggesting to separate the files.

If you have the same question regarding the TEMP file, please read this thread: http://sqlanywhere-forum.sap.com/questions/28934/move-tempdb-to-ram-any-theoretical-improvements You see, even the ram disk is not worth using it :(

(17 Jan, 06:45) Vlad
Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 17 Jan, 04:07

question was seen: 69 times

last updated: 17 Jan, 06:45