Converting to SQL server

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have built a db for a client which has a Backend (server) and Frontend (local pc):
The backend keeps corrupting and requiring constant repair. I am not sure why this is but I am
guessing that we are reaching Access's limits.
I am considering converting it to SQL server but I have no idea as to what's involved ie:
Do they need a separate server running the server app.
What (overview) is required to convert the existing Access 2000 to SQL Server?

Thank you for any help.
 
What is the compacted size of your Back-End?

I have a number of Back-Ends that are over 300 MB and they
work fine with none or very few corruptions. Others have
reported much bigger databases without any ptroblems.
Thus, I think the problem may be somewhere else.

Try Tony Toews' excellent article on corruptions:

<http://www.granite.ab.ca/access/corruptmdbs.htm>

Also check his article on performance:

<http://www.granite.ab.ca/access/performancefaq.htm>

It is often recommended to have a separate server to run
MS-SQL server but it is not compulsory. In fact the
Windows 2000 Small Business Sever package combines File
Server / MS-SQL Server / Exchange Server into 1 physical
server box.

Converting to MS-SQL server will require a fair bit of
modifications to your existing database, especially if you
have a lot of Parameter Queries, dynamic SQL String and if
you use DAO coding in the existing database (ADO is
recommended for MS-SQL Server Back-End).

If you still think of upsize to SQL server, get the book
Microsoft Access Developer's Guide to SQL Server by Andy
Baron and Mary Chipman and read it first.

HTH
Van T. Dinh
MVP (Access)



-----Original Message-----
I have built a db for a client which has a Backend
Click to expand...
(server) and Frontend (local pc):
The backend keeps corrupting and requiring constant
Click to expand...
repair. I am not sure why this is but I am
guessing that we are reaching Access's limits.
I am considering converting it to SQL server but I have
Click to expand...
no idea as to what's involved ie:
 
What (overview) is required to convert the existing Access 2000 to SQL
Server?

1) Use the upgrade wizard
2) Change code and forms that use the autonumber field before the record is
saved.
3) Modify DAO code to work with SQL Server.
4) Fix problems with any unusual code, SQL, etc, (unusual code doesn't port
well)
I am not sure why this is but I am
guessing that we are reaching Access's limits.
Click to expand...

Well, it's failures in your network software, but if it can encourage
you to buy more software from the same company, they will be willing
to call it an 'Access limit'

(david)
 
Back
Top