Hi Eleanor
We (exeGesIS) have been working on a SQL Server version for HBSMR for some time now, so I hope this may be useful...
There are three main aspects to your question:
1. The "application", or user interface through which you edit and view your data.
2. The database platform.
3. The data structure.
In your existing system, 1 and 2 are combined in MS Access.
If you change 2, then 1 could still be in Access, giving you the quickest and easiest solution, or you may decide to make a more radical change.
Moving data from mdb into SQL Server is usually fairly straightforward, and you could probably carry on using your existing Access application to view and edit this data with only minor tweaks.
On the other hand, you may also want to write (or acquire) a completely new user interface. There are lots of technology choices here, though this will be heavily constrained by your IT people's preferences and policies if doing this in-house. Developing a decent SMR/HER system from scratch in-house will be very expensive and time-consuming, particularly if you want good GIS integration, thesaurus terminology control, multi-media cataloguing, etc (and you can probably guess what I would really recommend...;-)
Changes to data structure (3) will have a bigger impact than the move to SQL Server per se, as the application has to be changed in line, whatever system it is written in.
Please get back to me if we can help in any way,
yours
Crispin
~~~~~~~~~~~~~~~~~~~~~
Crispin Flower
exeGesIS SDM Ltd.
Great House Barn
Talgarth
Powys
LD3 0AH
tel: 01874 713072/711145
fax: 01874 711156
email: [log in to unmask]
URL: www.esdm.co.uk
~~~~~~~~~~~~~~~~~~~~~
This email and any files transmitted with it are private and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient, the email and any files have been transmitted to you in error and any copying, distribution or other use of the information contained in them is strictly prohibited.
Nothing in this email message amounts to a contractual or other legal commitment on the part of exeGesIS SDM Ltd unless confirmed by a signed communication.
exeGesIS SDM Ltd will make every effort to keep its network free of viruses. However, the recipient of this message will need to scan this message, and any attachments, for viruses, as exeGesIS SDM Ltd can take no responsibility for any computer virus that might be transferred by this email.
-----Original Message-----
From: Eleanor Kingston [mailto:[log in to unmask]]
Sent: 06 April 2005 14:52
To: [log in to unmask]
Subject: SQL Server
Hi Everyone,
My Authority is currently undergoing a move away from databases held in MS Access (which includes our HER - designed in-house by the County Council) to SQL Server. As we were about to embark on quite a change in the structure of the HER database to conform with current data standards, it seems sensible to move over to SQL Server at this time.
My question is, has anyone else experienced this and have you got any advice/hints that would help us during the transition? Off-list replies welcome.
Thank you,
Eleanor
Eleanor Kingston
Archaeologist
Lake District National Park Authority
Direct Dial: 01539 792712
www.lake-district.gov.uk
This email contains information intended for the addressee only. It may be
confidential and may be the subject of legal and/or professional privilege.
Any dissemination, distribution, copyright or use of this communication
without prior permission of the addressee is strictly prohibited. Any views
or opinions presented are solely those of the author and do not necessarily
represent those of the Lake District National Park Authority. Although this
email and any attachments are believed to be free of any virus or other
defects which might affect any computer or IT system into which they are
received, no responsibility is accepted by the Lake District National Park
Authority for any loss or damage arising in any way from the receipt or use
thereof. Computer systems of this Authority may be monitored and
communications carried out on them recorded, to secure the effective
operation of the system and for other lawful purposes.
|