[dba-SQLServer] Upsizing and consolidating Access data into SQL Server

Steve Erbach erbachs at gmail.com
Wed May 16 14:59:55 CDT 2007


Bryan,

Very good questions!  This is a rather unique application.  The owner
of it developed it in Paradox for Windows when he had his own hazmat
consulting company.  He was hired by a local company to run its
environmental/legal department.  He allowed the company to use his
software for its required environmental reporting (EPA and Wisconsin
Dept. of National Racehorses).  I upgraded the Paradox app and then
recommended switching to Access.  He worked out arrangements with a
number of suppliers and sister companies to install the app.  I
support and install and upgrade all of them.  IT'S A PAIN!  But he's
the one that figures out if somebody needs to pay anything or not.  He
seems to think that the all-in-one location of the data and the code
will be an excellent idea.  I can hardly disagree.

As far as transmission over the Internet, as I said, the data is quite
innocuous, though we could set up an SSL certificate, I suppose,
couldn't we?

Thanks for your input.  I really appreciate it.

Steve Erbach
Neenah, WI
http://TheTownCrank.blogspot.com


On 5/16/07, Bryan Carbonnell <carbonnb at gmail.com> wrote:
> On 5/16/07, Steve Erbach <erbachs at gmail.com> wrote:
>
> > Of course, if the server goes down then everybody goes down. But the
> > positives, I think, would be ease of upgrading, keeping everybody at
> > the same revision level simultaneously, and low cost.
> >
> > Do you see any flies in the ointment here? I think it's very feasible,
> > but I'd welcome any cautioning voices.
>
> Does everyone automatically get updates or do they have to pay for
> them? What if someone doesn't want to or just doesn't pay for an
> upgrade?
>
> What if they don't want the data to travel on the 'net, but what it
> installed on their Intranet?
>
> Those 2 spring to mind quickly.
>
> --
> Bryan Carbonnell - carbonnb at gmail.com



More information about the dba-SQLServer mailing list