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

Jim,

» That sure is a pretty application. «

Why, thank you, Jim! I'll pass that along to my wife, Janet; she was
the graphic designer.

I don't think that going down will be a concern.  This application is
mostly used once a month to record data for the previous month to
report out to the various guvmint agencies.  It's time critical to a
degree, but everybody knows to get the info into the system on a
timely basis for monthly reporting.

I'm thinking that it's pretty workable, too.  The only question mark
with respect to the web host is what will the extra charge be for
additional SQL Server logins.  I think that would be the way to go
instead of using one master login to save a few bucks and then having
separate application logins.  I don't want anybody getting the idea
that they just have to have SQL Management Studio to get in to look at
their data in the raw.

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


On 5/16/07, Jim Lawrence <accessd at shaw.ca> wrote:
> Hi Steve:
>
> That sure is a pretty application.
>
> If going down is a concern some site can provide a fail-over scenario. When
> the DNS is setup one zone would point to one host and other zone point to
> another host. Each would have a synchronized data set. The Zone managers are
> multiple sites as well.
>
> Sounds like a very workable system.
>
> Jim
>
> -----Original Message-----
> From: dba-sqlserver-bounces at databaseadvisors.com
> [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Steve
> Erbach
> Sent: Wednesday, May 16, 2007 10:56 AM
> To: SQLList
> Subject: [dba-SQLServer] Upsizing and consolidating Access data into SQL
> Server
>
> Dear Group,
>
> I've been the chief designer for a vertical market application that
> was created with Microsoft Access 2003. The application has been
> installed in a handful of locations around the country, some
> single-user, some multi-user.
>