![]() I'm just saying that it's important to determine what the job duties really are. In your company, if everyone refers to the CRM as the "CRM database," this might be why her position is titled "DBA." I am not trying to diminish her role or yours whatsoever. It's possible that most of the job duties are CRM administration, rather than a full-fledged "DBA." The job title could be misleading. ![]() If you are managing reports and some automated functions, your background may be well-suited to take over the "DBA"s job. First, find out what you actually need to do. In small to mid-size companies outside of technology industries, it is common that the breadth and depth of technology skills of individuals and collectively is not the same as walking into a company with hundreds of different roles in technology.ĭon't fret. If you are really stepping into the shoes of a full, primary DBA role and don't have experience with SQL, even though you can get a lot of free training and resources here, I would ask your company to send you to some DBA courses. Ask her if she "manages" the "database" from the CRM application, or at the database level. Make sure your computer has all applications installed that she utilizes. Get logins and passwords to everything she has access to. While you have a chance, talk to your DBA directly. When you talk about "adjusting report" and making some "automatic import/export" functions, these could be features of the CRM application that you are using. I have seen some companies which use applications that have a relational database back-end, which has forever been left on auto-pilot. My guess is that you have likely been using a "User Interface" or the "Front End" of a database. Fyfe275, I'm inferring that by "CRM database," you are referring to working with a "Customer Relationship Management" database.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |