Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Multiuser / Networking / November 2004

Tip: Looking for answers? Try searching our database.

Upgrade Access 97

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Weste - 08 Nov 2004 14:24 GMT
We have a multi-user Access 97 application that we are considering upgrading.
Can someone tell me if there are any disadvantages of upgrading to mySQL vs
SQL Server 2000.  Thanks.

Weste
TJ - 09 Nov 2004 16:15 GMT
Cost is the primary concern.  SQL Server is much more expensive than
mySQL, albeit, it's also much easier to manage because of the toolset
built into the application.

Are you still going to use Access for the front end interface?  Access
97 has a tool for 'upsizing' the Access tables to SQL server.  You
might need to do some searching for the tool, but it is out there.  You
can still keep an Access front end and hit the SQL via ODBC.
TJ
TJ - 09 Nov 2004 16:17 GMT
Cost is the primary concern.  SQL Server is much more expensive than
mySQL, albeit, it's also much easier to manage because of the toolset
built into the application.

Are you still going to use Access for the front end interface?  Access
97 has a tool for 'upsizing' the Access tables to SQL server.  You
might need to do some searching for the tool, but it is out there.  You
can still keep an Access front end and hit the SQL via ODBC.
TJ
Weste - 09 Nov 2004 20:03 GMT
TJ,

Thanks for your response.  Right now we plan on keeping Access as the FE.  I
will do some searching for the tool you recommended.  Thanks again.

> Cost is the primary concern.  SQL Server is much more expensive than
> mySQL, albeit, it's also much easier to manage because of the toolset
[quoted text clipped - 5 lines]
> can still keep an Access front end and hit the SQL via ODBC.
> TJ
Tony Toews - 10 Nov 2004 06:21 GMT
>Cost is the primary concern.  SQL Server is much more expensive than
>mySQL, albeit, it's also much easier to manage because of the toolset
>built into the application.

OTOH you could use MSDE if the limits of 2 Gb file size and throttled
to 5 processes (which is *NOT* the same as 5 users).   And it's free.

Also see my Random Thoughts on SQL Server Upsizing from Microsoft
Access Tips page at
http://www.granite.ab.ca/access/sqlserverupsizing.htm

Tony
--
Tony Toews, Microsoft Access MVP
  Please respond only in the newsgroups so that others can
read the entire thread of messages.
  Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Weste - 10 Nov 2004 14:53 GMT
Tony,

Thanks for the link - alot of great information.  I have a question
regarding MSDE you mentioned.  You said it is limited to 5 processes and not
5 users.  So is a process something like running a query, report,etc.  My
database currently has about 200 users - 20 concurrent users.  The size is 75
MB.  Are there any tools out there that document the number of processes
running?  I would love to use MSDE but I don't want my users to see a
decrease in performance.  Thanks for your help.

> >Cost is the primary concern.  SQL Server is much more expensive than
> >mySQL, albeit, it's also much easier to manage because of the toolset
[quoted text clipped - 14 lines]
>    Microsoft Access Links, Hints, Tips & Accounting Systems at
> http://www.granite.ab.ca/accsmstr.htm
Tony Toews - 10 Nov 2004 21:26 GMT
>Thanks for the link - alot of great information.  I have a question
>regarding MSDE you mentioned.  You said it is limited to 5 processes and not
[quoted text clipped - 3 lines]
>running?  I would love to use MSDE but I don't want my users to see a
>decrease in performance.  Thanks for your help.

What happens is the sixth and subsequent process have to wait thief
turn.   If the processes are fast then this isn't a problem.  Ten
users running long reports simultaneously would be a problem but
that's unlikely.

There is something built in that you can interrogate to see if you've
hit the throttling limits.

One person posted that he'd successfully had about a hundred users on
an MSDE system without any problems.  But clearly that may be a system
which was highly optimized for SQL Server and he'd spent some
considerable time tweaking.

Tony
--
Tony Toews, Microsoft Access MVP
  Please respond only in the newsgroups so that others can
read the entire thread of messages.
  Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.