Access vs MSDE

Currently developing a website with Access Db at the backend which needs to synchronise with another Access Db. I have assumed that I should migrate this to MSDE with replication to go live ... but can/should I stay with Access ?
Replication is possible within Access, & is easier to setup. However, you
then need to run the Syncronization Manager which has the annoying 'feature'
of leaving a taskbar item running at all times.
Your requirement to upsize to SQL Server should consider more than just the
need for replication such as:
1. The number of concurrent users expected.
2. The required availability of the db.
3. The backup requirements.
And many more...
Many books on Access & SQL Server discuss this in detail, but if your only
reason for upsizing to SQL Server is for replication, it probably isnt
necessary...
Cheers,
James Goodman
"Sarah" <anonymous@.discussions.microsoft.com> wrote in message
news:6812B4CA-F321-4312-8EF6-8077C25215D4@.microsoft.com...
> Currently developing a website with Access Db at the backend which needs
to synchronise with another Access Db. I have assumed that I should migrate
this to MSDE with replication to go live ... but can/should I stay with
Access ?
|||Thanks James.
I take your point re the other requirements and I'm trying to knock them off one by one but I'm finding it quite difficult to get any definitive answers (especially given the MSDE 'Governor' problem). Also its difficult to judge what some of the variables
may be (e.g. concurrent users could be loads if the web-site is popular or zilch if not!). I'm having to juggle the needs (and lack of funds!) of a small business start-up and guess a lot of it!
Could you recommend any particular books/sites that do good comparisons ?
|||There are licensing implications with making SQL Server data available from
the intranet & internet. I believe they are as follows:
For intranet access Per Seat licensing is ok, as long as you have enough
CALS to cover all users.
For internet access, Per Server licensing is required.
You should therefore be using SQL Server Standard edition at least.
If keeping costs down is important, I would probably recommend using Access.
You can upsize fairly simply should it be required in the future, but you
cannot easily downsize.
This link might help you with regards to the governor:
http://msdn.microsoft.com/library/de...r_sa2_0ciq.asp
http://msdn.microsoft.com/library/de...sderoadmap.asp
Doing a google groups search for similar posts will probably return some
good results as well...
Cheers,
James Goodman
"Sarah" <anonymous@.discussions.microsoft.com> wrote in message
news:BF1BCA42-9559-4C22-A31F-6314AA80F2A6@.microsoft.com...
> Thanks James.
> I take your point re the other requirements and I'm trying to knock them
off one by one but I'm finding it quite difficult to get any definitive
answers (especially given the MSDE 'Governor' problem). Also its difficult
to judge what some of the variables may be (e.g. concurrent users could be
loads if the web-site is popular or zilch if not!). I'm having to juggle the
needs (and lack of funds!) of a small business start-up and guess a lot of
it!
> Could you recommend any particular books/sites that do good comparisons ?
|||Thanks for the links - the second one is really good!
fyi I think the licensing is OK for MSDE on the web tho' (see http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp)