nuct
Programmer
- Sep 5, 2001
- 103
Hi,
I have just landed a DBA job which starts on Monday. The problem is to get it I had to tell a small lie about my employment history. Basically I created a fake DBA job. I think sometimes you have to tell white lies to get ahead.
I've got my MCDBA/MCSA so I a have a good understanding of SQL Server 2000, and I know SQL well, but of course things are always different in practice. So what I'm really asking is if someone could give me some hints which can help me to be as convincing as possible because I want to impress them.
The company has 35 ish employees, a call center environment and SQL Server 2000/Access databases. It is a new position.
Here's some specific questions, but if there is anything else please tell me:
1. What does a real life DBA's typical day involve?
2. What projects should I suggest for myself?
3. What is the normal procedure for backups, is it normal for someone to take a backup home with them in case of fire/flood etc.
Any help, however small, is massively appreciated.
Thanks,
Pete.
I have just landed a DBA job which starts on Monday. The problem is to get it I had to tell a small lie about my employment history. Basically I created a fake DBA job. I think sometimes you have to tell white lies to get ahead.
I've got my MCDBA/MCSA so I a have a good understanding of SQL Server 2000, and I know SQL well, but of course things are always different in practice. So what I'm really asking is if someone could give me some hints which can help me to be as convincing as possible because I want to impress them.
The company has 35 ish employees, a call center environment and SQL Server 2000/Access databases. It is a new position.
Here's some specific questions, but if there is anything else please tell me:
1. What does a real life DBA's typical day involve?
2. What projects should I suggest for myself?
3. What is the normal procedure for backups, is it normal for someone to take a backup home with them in case of fire/flood etc.
Any help, however small, is massively appreciated.
Thanks,
Pete.