Stack Exchange Network

Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange
141

The position requires a broad spectrum of knowledge ranging from development to system administration and even management. Not only must a DBA know about backup, recovery, internal operations, memory and security, but also how to communicate with both developers and management. A DBA could be giving a high level presentation to management, helping a ...


57

Becoming a DBA actually demands a great measure of experience but it can basically come from only four different paths: Being a developer and making a segue to a DBA Being a developer and being drafted as a DBA Training straight from college/trade school to become a DBA Being a SysAdmin and making a segue to or pulling double-duty as a DBA Being a ...


37

Database Administration is difficult because of two reasons Slow feedback If one makes a bad decision in the role of a software architect, it usually takes longer to get negative feedback compared to a programmer. The programmer can often become aware of the error during compilation or while running tests, which means that the learning cycle is quite fast. ...


27

It is pretty easy to be a bad DBA Seriously though, a DBA usually has special responsibility for something that is often critical to the success or failure of a business: its data If you run a company then you may well be keen to employ competent experienced people in that role I don't think it is a question of 'easier' or 'harder' - just a question of ...


18

I know a lot of Database Administrators and they are all over 28-29 years old. Is all database administration like that? Most good, solid programmers I know are also at least 25 years old. I imagine there is a correlating factor to age + experience = good coder. ;) I mean, is this about getting experience more than at least 7-8 years? Or is being a ...


18

In my opinion, being a Database Administrator is easy...until something breaks that threatens the company and the burden of fixing and restoring whatever it is is on your shoulders. Being a Database Administrator (or Network or System Admin) is a position that requires a certain maturity level. It takes someone who works well under pressure. That's not to ...


16

I don't think that being a DBA is hard. Becoming one was though.


14

I wanted to answer to add another aspect not well discussed above: field of vision. There are wide varieties of roles for developers and some (for example, device driver development, or developing operating system schedulers) require a very narrow field of vision and an ability to delve deeply into a small problem and look at it from a purely technical ...


11

Yes. There is a whole web site devoted to it: Agile Data I'm using it now for a brand new project. Also see: Should you design the database before the application code is written?. My answer there doesn't capture what I do now: 2 week sprints, good enough for that sprint. As per the Agile Data site. I find it a good practice. It focuses on the here and ...


10

I want to start by saying everything I do is SQL Server so those are the examples I give. In general however this applies to any form of code regardless of system. Let's start by breaking this down a bit. Upgrades You have a system and are about to upgrade some or all of it. For example upgrading an instance from SQL Server 2012 to 2014. At this point ...


9

As developer, not a full-time DBA, I use Postgres for some of my work. But it is not my focus. I found Postgres very confusing and frustrating when getting started. After a long career using 4D, I was an pro in relational database design and normalization, but a newbie with SQL and "black-box" database engines. Below is a list of the resources that helped me....


9

When Codd defined the relational model he defined a set of operators which could be applied to relations. In specifying a relational algebra, much like specification of an integer algebra, we are able to use symbols in place of relations to solve queries. These operators are subject to the same algebraic properties that integer algebra operators (+, -, *, /...


8

There is another path, slightly different form the ones listed. Start as a developer, then become a database designer, then become a DBA. This path was more prevalent about thirty years ago, when databases began overtaking file based applications big time, and people with database expertise were few and far between PS: When I was an ex-programmer turned ...


8

Besides the classics by Codd & Date, here are the DBA books on my shelf: DBA Survivor by Thomas LaRock is a must-read for beginning and evaluating your DBA career. This book is the reason why I'm on StackExchange. The Data Warehouse Toolkit classics by the Kimball Group is the most authoritative guide on dimensional modeling and data warehousing. Since ...


7

I'm rather at the start of my DBA journey, but here are a few of the reasons why people can find this job hard... It's hard because: you have a lot of responsibilities: people can come and go in a company, but for quite a few of them, their most important asset is their data. You're responsible for it and have all powers over it. As the saying goes, with ...


7

I would spend sometime over at the Teradata Developer Exchange, Teradata Questions (currently disabled), and the Teradata Forum. There is a wealth of information to be gleaned from these sites. There is an Express version of Teradata that can be downloaded from here. This will allow you the opportunity to experiment with Teradata on your own computer. The ...


6

Have a look at: http://sqlzoo.net/ This seems to be what you are looking for.


6

Found these http://www.simple-talk.com/community/blogs/lionel/default.aspx http://sqlzoo.net/ https://forums.oracle.com/forums/thread.jspa?threadID=666829


6

It shouldn't take long to get up to speed to a reasonable degree if you've used another RDBMS. Read some guidance on PostgreSQL for MySQL users to help you adapt to sequences vs auto_increment, ANSI-standard quoting (though you should be using that in MySQL already), the stricter data type checking, how authentication and roles work, psql's backslash ...


6

General notes First of all, T-SQL and MDX are 2 completely different beasts. SQL is intended to query tabular relational data, while MDX is intended to query multidimensional data. I'll start with addressing your question about common mistakes. In my opinion the most common mistake is to try and apply SQL knowledge to MDX. You really need to get into the ...


6

Q1: Previously, I have purchased other Microsoft Certification books and have normally got a PDF version, along with the printed book. Is this not the case anymore? Am I missing a disk or something? On the page you linked to, there were 3 options: book, ebook, and book + ebook. You would need to buy the book + ebook option if you wanted both. Q2: The book ...


5

There are two sites which really stand out for learning SQL, especially Oracle (for MySQL see below). Oracle forums. Pay particular attention to the posts of Frank Kulash and Solomon Yakobson (sometimes things of rare beauty) but anyone with a rep of > 20k merits attention. Check the rankings on the forums page. Orafaq forums. Solomon Yakobson (again), ...


5

I recommend reading the following appendix found in a few of Chris Date's more recent books: Two Cheers For Normalization Normalization is far from being a panacea, as we can easily see by considering what its goals are and how well it measures up against them... I must make it clear that I don't want my comments in this section to be seen as ...


5

I became a dba at the age of 25. It took me 6 months from the time I started studying to get certified and 2 months later I had a job. I think determination definitely plays a major part. For me it was not hard getting the job. All it took was will power to study and showing that I was capable of learning what ever is put in front of me. I will say that all ...


5

Being a DBA also means you are proactive instead of reactive. You have to be able to imagine what the future holds and plan accordingly. This involves working hard...once, many, many times, and if you do it right, the reward is a complete lack of name recognition. :-) You also have to have the ability to say "no" to people (bosses included) and ...


4

As someone who considers himself primarily a SysAdmin and secondly an accidental DBA, I think part of it comes down to the amount of knowledge required to stand on your own and do the job, or perhaps more importantly, to understand the job. The old MCDBA certification sums it up quite well I think. It required four exams to be passed, a SysAdmin exam, a ...


4

I know what you feel, I have 3 years working with MySQL, and in my case I always test the DML queries that can modify or break any information on every table/database/Slave-replication. It's always the safest way to test your query before you run it. There's no way to know if your query can put your data information at risk. The only way is knowing your ...


4

I strongly feel you can be successful as a DBA without taking a formal course in relational algebra, just like you can be a successful programmer without taking a formal course in discrete math. The need to take a course in relational algebra would very much depend on your career path/goals. See this question on Programming StackExchange. The OP wanted to ...


3

I've been doing Agile development for more than four years, including my SQL Server projects, and I really like it. I think it is important to understand why and when Agile is useful, from the perspective of the whole system, and general purpose Agile-related books such as the following fit the bill: " Agile Principles, Patterns, and Practices in C#", " ...


Only top voted, non community-wiki answers of a minimum length are eligible