Documentation is the constant burden of many a computer professional – but why? Because it is for-the-most-part a static, legacy reporting system.
The usefulness of documentation is undoubted when dealing with other professions, but the curse is that it needs to be maintained. And in a fast changing environment – like in the computer industry – documentation needs to be dynamic.
Spreadsheets should update themselves for example. Have you ever seen a correct server list?
So please please, file static documentation with telephone directories – in the bin 🙂
This is a record of the steps I performed to enable replication between MySQL5.0.77 on RHEL and 5.5.25 on WindowsXP.
1. ensure two-way connectivity with pings.
2. make mysql on windows easier to work with by copying mysql.exe and mysqldump.exe to c:windowssystem32.
3. On the Replication-Master (RHEL) I made a copy of /etc/my.cnf then amended the original using VI adding the lines
“log-bin=mysql-bin” and “server-id=1” within the [mysqld] section.
I rebooted and tested that binary-logging was ‘on’ with the command “show variables like ‘log_bin'”.
4. On the WindowsXP / 5.5 / Slave machine I copied then amended the file “c:program filesmysqlmysql server 5.5my-large.ini” (note: I chose ~large.ini as my machine had 512mb memory).
I then confirmed all other conflicting settings were commented out (EG: server-id=1) and sdaved the file.
I feel that Microsoft DBA’s are not so worried about knowing every nook-and-cranny of their DBMS because Microsoft can always be relied on to find a specialist to help out 🙂
Oracle DBA’s on-the-other-hand know that Oracle PLC only does databases, not Support or Documentation (ok I may be exaggerating a bit). So Oracle DBA’s are on their own, and really need an intimate understanding of their particular DBMS internals.
I’m not inferring the superiority of one tribe over the other, just noting the difference 🙂