RE: How Big A Dump File Can Be Handled?

> From: Thorsten Schöning
> Sent: Wednesday, 21 August 2013 17:21 PM
> Guten Tag Geoff Field,
> am Mittwoch, 21. August 2013 um 08:29 schrieben Sie:
>
> > I've just realised that my concern was based on a power-of-2
> > limitation that means that a 32-bit signed integer would
> roll over at
> > the 2GB mark, with an unsigned roll-over at 4GB. It's possible the
> > Windows Server 2003 file system might have started to
...
> You didn't seriously thought that a Windows Server 2003 has
> such limitations?! If you installed on FAT32 you made
> something really wrong. ;-)

Ah, but it wasn't ME that did the install.

> > I really should have done it all using a scripting language of some
> > sort, too. I've told myself it's really too close to the
> end of the
> > process to think of *that* change now, except I've just managed to
> > quickly throw together a batch file to do the job.
...
> I created a powershell script to convert my 1.4 repos to 1.7
> some months ago, few months later we moved all repos to our
> Ubuntu development server and last month or so I upgraded svn
> to 1.8, without the possibility of a full dump/load because
> of my not working script anymore. One shouldn't start with
> platform specific console scripting anymore unless it's about
> really trivial stuff. It's to easy these days to change platforms.

To me, the copy is pretty trivial (if somewhat tedious) and unlikely to be repeated.

Changing platforms, however, would be distinctly NON-trivial in our circumstances. The servers are administered by a whole other department, with their platform inertia somewhat built-in.

Regards,

Geoff

-- 
Apologies for the auto-generated legal boilerplate added by our IT department:
- The contents of this email, and any attachments, are strictly private
and confidential.
- It may contain legally privileged or sensitive information and is intended
solely for the individual or entity to which it is addressed.
- Only the intended recipient may review, reproduce, retransmit, disclose,
disseminate or otherwise use or take action in reliance upon the information
contained in this email and any attachments, with the permission of
Australian Arrow Pty. Ltd.
- If you have received this communication in error, please reply to the sender
immediately and promptly delete the email and attachments, together with
any copies, from all computers.
- It is your responsibility to scan this communication and any attached files
for computer viruses and other defects and we recommend that it be
subjected to your virus checking procedures prior to use.
- Australian Arrow Pty. Ltd. does not accept liability for any loss or damage
of any nature, howsoever caused, which may result
directly or indirectly from this communication or any attached files.