Re: migrating from MSAccess...
From: Liz (liz_at_tiredofspam.com)
Date: 04/28/04
- Next message: Aaron Bertrand [MVP]: "Re: connect to named instances"
- Previous message: Mark Jerde: "Re: Enterprise Manager "New Window from Here" Hack or Whatever"
- In reply to: clamfuddle: "migrating from MSAccess..."
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 27 Apr 2004 20:03:10 -0500
"clamfuddle" <vader1 at flash.net> wrote in message
news:ewGm#TKLEHA.624@TK2MSFTNGP11.phx.gbl...
> Our small tech office just got SQLServer2000 and until now we've been
> using MSAccess for some simple databases.
>
>
> We currently (due to MSAccess size limits, mostly) have separate databases
> for each
> client, but the tables for each are clones of each other.
>
> I'm presuming that you'd want to place all these tables into one SQL
server
> table, and add a key field to show which client the records belong to.
That
> would require adding a field and changing quite a few related
post-database
> processing programs, and complicate recovery if one of us imports data but
> gives it an incorrect client value.
with this amount of information, it's hard to know exactly what you would
want to do .. but, keep in mind that the whole purpose of using an RDBMS
like SQL2K is **sharing** data; implemented reasonably well, your
synchronization issues should abate, not escalate .... yes, you have some
work and some "complications" ahead of you but that's the way the game works
> However, I'm wondering about performance and multi-user issues, and
> generally
> wondering what the true "Best Practice" would be - combine them or keep
them
> separate.
well, we know nothing about your data and how it will be accessed, updated,
etc ... but with a reasonable hardware platform it's hard to imagine that
you can't support three users VERY comfortably
> If combined, we could use one Access front-end, and each person (3 of us)
> keep a copy
> of that front-end linked to the master tables on the server. Or would you
> keep one copy
> of a front-end on the server and each of us just use a shortcut to it?
>
> As we need to add queries, I can see synchronization problems if we have 3
> separate front ends, etc. etc. etc.
that's the problem you have today and the one you're beginning to get rid of
.. you need to read up on the basics of client-server computing; someone
here recommended Kalen Delaney's book, "Inside SQL Server 2000" a bit
earlier (to me, actually .. but I've been through its predecessor editions)
... I think it's a good choice and recommend you buy it tomorrow.
> I'm just hoping to get off on the right foot as we go about perhaps
upsizing
> our databases.
>
> Any help or references would be greatly appreciated.
>
> Thanks for your time,
> Bryan
>
>
>
- Next message: Aaron Bertrand [MVP]: "Re: connect to named instances"
- Previous message: Mark Jerde: "Re: Enterprise Manager "New Window from Here" Hack or Whatever"
- In reply to: clamfuddle: "migrating from MSAccess..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
