|
|
Posted by John Bell on 09/06/05 21:13
Hi
If you are having a consultancy migrate/install this packaged solution then
you would need to state that the system will have to included scheduled
maintenance. I don't know the package but they may provide their own front
end administration tool, which should be suitably documented. This should
cover most day to day issue but you may also require support if something
more serious happens.
As far as SQL Server is concerned you may want to look at books online and
the sections on
"Automating Administrative Tasks", "Backing Up and Restoring Databases", "
Monitoring Server Performance and Activity" and "Rebuilding an Index"
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.mspx
There is a specific newsgroup for Great Plains -
microsoft.public.greatplains as well as general accounting newsgroups and
they may help on advice as you will also probably need support on using the
application as well as maintaining the database
It may help to browse:
http://www.microsoft.com/BusinessSolutions/Community/GettingStarted.mspx
John
"TheScullster" <phil@dropthespam.com> wrote in message
news:A8mdnRQUcufeMoDeSa8jmw@karoo.co.uk...
> Hi all
>
> Sorry if this is such a mega dumb question for this group, but what
> exactly is involved in maintaining/supporting a SQL database?
>
> My company is looking at accounting software "Great Plains" which they
> intend to run on SQL server.
> Having only had experience of a split Access database, this is something
> of a quantum leap for me!
> The only maintenance I do on the Access version is a scheduled nightly
> compact/repair on the back end and have the front ends set to compact on
> close.
>
> So what is involved with the SQL database?
> Is it straightforward, or should I be talking the company into paying for
> yet more "maintenance/support" for someone to remote in weekly and perform
> a similar function?
>
> Any help appreciated.
>
> Phil
>
Navigation:
[Reply to this message]
|