|
|
Posted by John Bell on 09/09/05 10:57
Hi Oscar
A couple of questions that may help Phil!
"Oscar Santiesteban Jr." <oscarsantiesteban@worldnet.att.net> wrote in
message news:dN5Ue.212144$5N3.93311@bgtnsc05-news.ops.worldnet.att.net...
> Phil,
>
> We have been using a Billing system for the City's Water, Sewer, Garbage,
> and Storm Water for the past 6 years. We started using this system when
> Great Plains was still their own company, and not part of Microsoft. The
> system has never had any problems. I run a DBCC on the database, and
> reindex every weekend. I do full backups every night and transaction log
> backups every hour.
Was this set up by the consultancy or by you?
What training was included in the install?
> We have never had a need to call Great Plains, we
> mainly called our vendor with problems in the software.
I would assume this is things recoverying from incorrect configuration or
programming problems rather than database (engine) issues per-se?
> You will notice
> however that the Great Plains developers were smoking some bad weed when
> they developed this system.
It was probably tax deductable?
> Any system that names their tables with
> "zx00012234" for example are crazy. The people of Remedy (formerly of
> Peregrine) also suffer from halucinations and also use this crazy method.
Wierd table names in Accounting software is not uncommon!!
John
>
> Just as an FYI, the Great Plains system is developed in a language called
> "DEXTERITY". There is some sort of VBA add-in which will allow you to
> develop forms in Visual Basic.
>
>
> "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]
|