Regular readers of my blog will know that I have written three books this year. We are currently reviewing readers comments about SQL Server Interview Questions and Answers. I am sorry to announce that we made a mistake but happy to add that we have corrected it. We will pay closer attention to the error and make sure that it does not happen again. Writing a book is a lengthy very interesting process. I have had an excellent experience in writing my recent book SQL Server Interview Questions and Answers; we had so much fun and few moments of stress, too.
One of the interesting questions I recently received is how many people actually touch the manuscript of the book before it goes to the publisher. Now this number may vary, but here is how many people touched our book’s manuscript.
With this many people collaborating, keeping organized was our main concern. There were multiple people working together and most of the time we all were working parallel to each other on various part of the book. We kept on increasing the versions of the Word documents which we were all sharing. In the end the final version was sent to the printer. In our book there were two kinds of inaccuracies – 1) Ones we overlooked and did not correct, and 2) Ones we noticed but missed while collating various versions.
Before the book was published, everybody involved (every single person who contributed to the book in any capacity) had decided that if any errata was found, the next version must not have that error and we should maintain an error log. It has been 60 days since the book has been published and we have received quite a lot of communication on the book. The number one request is that many want a second part of the book, I am overwhelmed with your support and love.
Here is the page where we are listing all the errata of the book, if you are reading the book and you find anything which you would like to share with us – you are welcome to send us an email at books “at” sqlauthority.com. It does not matter if it is an English grammar error or technical inaccuracy – we value your input on any and all points. We aspired to be as close to perfect as possible and the first step is to accept our mistakes. Once we know the mistake, we will not repeat it and promptly correct it.
I know that I am looking forward to hearing from my readers about what they loved and what they’d like to see changed, and I’m sure my fellow collaborators would like to hear from you, too. Thank you again for all your support.
Reference: Pinal Dave (http://blog.sqlauthority.com)