Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Unload file

Status
Not open for further replies.

pto

IS-IT--Management
Feb 14, 2002
37
0
0
US
Does anyone know how the unload file is generated. For example we have a 24 GB database and during the unload the files are segmented into 2GB, my question is does anyone know what order the data is being pulled? Any help is greatly appreciated.[2thumbsup]
 

SQLBase 7.5.x removes the 2GB limit for SQLBase databases installed on an NT server - that's the good news.
The bad news is that the 2GB limit remains for unload files that exceed the 2GB limit.

If your SQLBase database creates an unload file that is greater than 2Gb then you have two options.

OPTION 1:
You can try the compress option to keep the unload file smaller than 2GB. The syntax for that is
UNLOAD COMPRESS DATABASE <PATH\FILENAME>;
For example:
unload compress database c:\temp\mylive.unl;

If the compressed mylive.unl file is less than 2Gb then you do not need to do a segmented unload/load but you do have to use the compress keyword when you load the database. For example:

load compress sql c:\temp\mylive.unl;

Note that a compressed unload file cannot be opened & edited by a text editor as an uncompressed unload file can.

OPTION 2:
You can perform a segmented unload/load which is a bit more work but if the compressed unload file is greater than 2GB you don't have a choice.

So the only real difference between a segmented unload and a standard unload is the control keyword.

Hope this helps
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top