🚀 go-pugleaf

Doug,

As a full time DBA (database administrator) with experience of DB2,
Oracle, SQL Server (Sybase and MS) and Informix here is my IMHO !!!

OS platform : I wouldn't trust any database server of any importance
to an MS operating system (although unfortunately my management think
otherwise - until we lose "a big one").

So I'd recommend you use RedHat (7.1 works very nicely for me).

That kinda rules out SQL Server !!!

Oracle is good from a programmer's point of view, but a real dog from
an admin point of view.

DB2 is easier to learn, robust, more ANSI standard, gives you all the
features of Oracle and more and (best of all) you can get Personal
Developer's Edition for free.  You can't use it for production use,
just for standalone development, but you can try it out and see how
you like it.

If you need any help at all, contact me through the address on my web
page (http://www.bojnice.com).

I can probably give you a hand to get you started if you want.

Phil Nelson
Senior DBA
Scottish Widows and Bojnice Database Consulting

On Sun, 01 Jul 2001 00:17:02 GMT, "Doug Gentry" <None@home.com> wrote:

>At work we get an email from HR every Week telling us at the helpdesk who is
>going to be terminated and on what date. Then when the date comes up we
>disable the account and start to remove their network privileges, deleting
>email account  and so on and so forth. Now comes the fun part. During the
>week we get all these emails from HR telling us that this person or that
>person will NOT be leaving on this date but will be leaving at a later date.
>We then have to remember when these peoples dates have changed.  I was
>thinking to myself, Gosh, this needs to be put into a database of all the
>employees and when someone is getting ready to leave we in the helpdesk can
>see up to the minute information on these employees. I'm leaning towards the
>idea that HR should have a company wide Employee database and when a box is
>selected (lets call it "Terminate") that would open a page where they can
>enter the date when that person will be leaving. Then we at the helpdesk
>would have access to that page. Anytime HR would make a change to those
>fields it would update the page at that moment. Then we could go about our
>business without having to track down various emails relating to these
>people.
>
>As a learning project and maybe get noticed a bit. (Blush blush..self
>serving bastard aren't I?) Anyway. I would like to build a kind of small
>demo database and take it to work and show them what we can do. I'm running
>Win 98 on this drive and have Access 2000, But I also run Linux RH on my
>other drive.
>
>1. Should I do this on 98 or RH? I'm leaning towards RH myself.
>2. Which or what should I build it with? Oracle, Mysql? Or what? I'm looking
>for suggestions here.
>
>3. I would also like to do it with a webpage where HR can go and enter the
>data and we can get the data output on the page with ASP.
>
>4. Now, the company is running NT servers on a novell network and NT
>workstations with some 95 and 98 workstations. Also they're using Lotus
>notes.. GAKkkk.. BUT.. they are going to be moving to Win 2000 servers and
>Win 2000 workstations and  exchange, except I did hear something in the
>works about ME.
>
>GAkkkkkkk... way too much to do hu?  I am reading everything I can get my
>hands onto but I'm running into a slight problem of information overload adn
>then everyone says their product is SOoooo much better than the others. I'm
>starting to get confused with this stuff now. So if anyone can set me
>straight and point me in the correct direction. I'll even settle for your
>humble opinion on what you think.
> I would be very appreciative.
>
>Thanks So much.
>Doug Gentry
>
>
>
>