[thelist] Large Monthly File Imports and Exports

[TJ]

Chris,

The DO want to use JET/Access.  I am thinking this is not a good idea.  In
my tests, its choking on the data but it IS loading it all.  I think Access
is wrong, but they are writing the check...

Express versions of 2005/2008 say they are 4G file limits, which is OK for
this.  It is an internal tool, but MySQL has been ruled out.  They only have
1 "tech" guy and he's got way too much stuff to manage.  Adding MySQL is out
of the question unfortunately.

This must be automated such that no one needs to worry about anything other
than pushing "start" and getting notified when its done.

Any idea if SQL Server 2000 is still "for sale" legitamately?  I see them on
eBay but are these legit copies?  I know MS still supports 2000 until 2013 I
believe.  If I could get a copy of SQL 2000 I could whip up some DTS
packages and install it on their box in no time and they'd be very happy.
I'd even try to slap an Access front end - though VB would do the trick just
as well.

Thanks Chris!

Anyone else?


On 7/3/08, Chris Anderson <Chris at activeide.com> wrote:
>
> > files are approaching 2G in physical size.
> ...
> > The client wants this done in Microsoft Access (2003).
>
> LOL (Sorry - I was envisaging them wanting to import that into a JET
> database rather than using Access as the front-end)
>
>
>
> > The Express editions of 2005 and 2008 are free to download and use but
> > they wont give them DTS (SSIS).
>
> They also have size limits (which are around the 2Gb mark IIRC)
>
> > I have a developer copy of SQL Sevrver 2000
> > however I am unsure if this can be "distributed" with a setup program.
>
> No it cannot
> If you went the SQL Server route, they would be required to use Standard
> at least (the "smallest" version that isn't Express which has been ruled
> out)
>
>
> > I am thinking BCP or some bulk
> > import and slap a user interface on it with VB 6 and add some
> "control"
> > tables in SQL Server 2000, to allow them to rerun exports and to do
>
> Sounds good.
> The only tricky bit may be if the file is corrupt in any way (the
> handling of structural file problems will be with the bulk loading tool
> you use), but that's the nature of loading data in bulk!
>
> > they
> > dont have SQL Server 2000.
>
> Have you considered MySQL?
> It has bulk import facilities as well (LOAD DATA INFILE [1]) and can
> support the sizes you are looking at - and for free as long as you don't
> sell it (and it sounds like an internal tool)
>
>
>
> [1] http://dev.mysql.com/doc/refman/5.0/en/load-data.html
> --
>
> * * Please support the community that supports you.  * *
> http://evolt.org/help_support_evolt/
>
> For unsubscribe and other options, including the Tip Harvester
> and archives of thelist go to: http://lists.evolt.org
> Workers of the Web, evolt !
>